2 |
Approval of the agenda |
|
R4-2014000 |
Agenda for RAN4 #97-e |
Apple (UK) Limited |
R4-2014001 |
RAN4#96-e Meeting Report |
ETSI MCC |
R4-2016599 |
RAN4#97-e E-meeting Arrangements and Guidelines |
RAN4 Chair (Apple) |
R4-2016602 |
RAN4 Meeting Efficiency Improvements |
RAN4 Leadership |
3 |
Letters / reports from other groups / meetings |
|
R4-2014147 |
LS on updated Rel-16 RAN1 UE features lists for NR |
RAN1 |
R4-2014148 |
LS on updated Rel-16 RAN1 UE features list for LTE |
RAN1 |
R4-2014149 |
LS on updated Rel-16 RAN1 UE features lists for NR |
RAN1 |
R4-2014150 |
LS on updated Rel-16 RAN1 UE features lists for LTE |
RAN1 |
R4-2014151 |
Reply LS on UE capability |
RAN1 |
R4-2014152 |
LS on evaluation methodology for connected mode UE power saving enhancements |
RAN1 |
R4-2014153 |
Reply LS on UE declaring beam failure due to LBT failures during active TCI switching |
RAN1 |
R4-2014154 |
LS on evaluation methodology for UE power saving enhancements |
RAN1 |
R4-2014155 |
Reply LS on Rel-16 UE feature lists for NR DAPS |
RAN2 |
R4-2014156 |
Reply LS on exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI |
RAN2 |
R4-2014157 |
LS to RAN4 on measurement requirement for eMTC UE in RRC_INACTIVE |
RAN2 |
R4-2014158 |
LS on UE capability for V2X |
RAN2 |
R4-2014159 |
LS on simultaneous Rx/Tx for inter-band NR-DC |
RAN2 |
R4-2014160 |
LS on cell-grouping UE capability for synchronous NR-DC |
RAN2 |
R4-2016598 |
FREQUENCY ARRANGEMENTS FOR IMT IN THE BAND 470 |
APT Wireless Group |
R4-2017799 |
REPLY LIAISON STATEMENT TO 3GPP RAN4 |
ITU-R Working Party (WP) 5D |
R4-2017800 |
LS to 3GPP RAN WG4 on Release 15 of the IMT harmonised standard |
MSG TFES |
R4-2017801 |
Reply LS on UE capability on wideband carrier operation for NR-U |
RAN1 |
R4-2017802 |
Reply LS on number of configurable CSI-RS resources per MO |
RAN1 |
R4-2018002 |
Reply LS on updated Rel-16 LTE parameter lists |
RAN2 |
R4-2018003 |
Reply LS on definition of NR V2X con-current operation |
RAN2 |
R4-2018004 |
Reply LS on FR1 intra-band UL CA UE capability |
RAN2 |
4.1 |
System Parameters Maintenance [NR_newRAT-Core] |
|
R4-2015176 |
CR to TS 38.307 Release independence support of new channel bandwidth from Rel-15 |
ZTE Wistron Telecom AB |
R4-2016524 |
On channel space for CA |
Huawei, HiSilicon |
R4-2016525 |
CR on channel space for CA |
Huawei, HiSilicon |
R4-2016526 |
CR for 38.101-1 channel space for CA_Rel16 |
Huawei, HiSilicon |
R4-2016527 |
CR on channel space for CA |
Huawei, HiSilicon |
R4-2016528 |
CR for 38.101-2 channel space for CA_Rel16 |
Huawei, HiSilicon |
R4-2016603 |
Email discussion summary for [97e][101] NR_NewRAT_SysParameters |
Moderator (ZTE) |
R4-2016779 |
LS to RAN5 on nominal channel spacing calculation for two carriers at band n41 with 40MHz and 80MHz channel bandwidths |
RAN4 |
R4-2016945 |
Email discussion summary for [97e][101] NR_NewRAT_SysParameters |
Moderator (ZTE) |
4.2.1 |
[FR1] Maintenance for 38.101-1 [NR_newRAT-Core] |
|
R4-2015031 |
CR to TS 38.101-1: Correction on the Aggregated Channel Bandwidth |
ZTE Corporation |
R4-2015032 |
CR to TS 38.101-1: Correction on the Aggregated Channel Bandwidth |
ZTE Corporation |
R4-2016041 |
CR Removal of Band 10 protection 38101-1 Rel15 |
Skyworks Solutions Inc. |
R4-2016604 |
Email discussion summary for [97e][102] NR_NewRAT_UE_RF_Part_1 |
Moderator (Nokia) |
R4-2016784 |
Reply LS on structure of NR CA reference sensitivity requirements in 38.101-1 |
RAN4 |
R4-2016946 |
Email discussion summary for [97e][102] NR_NewRAT_UE_RF_Part_1 |
Moderator (Nokia) |
4.2.1.1 |
Maintenance for Transmitter characteristics [NR_newRAT-Core] |
|
R4-2014254 |
CR to 38.101-1: UL MIMO EVM and emission requirements update |
Qualcomm Incorporated |
R4-2014255 |
CR to 38.101-1: UL MIMO EVM and emission requirements update |
Qualcomm Incorporated |
R4-2014256 |
FR1 transmitter requirements for 2-layer UL |
Qualcomm Incorporated |
R4-2014307 |
Clarification of additional spurious emission requirements on two bands uplink Inter-band CA(R15) |
SoftBank Corp. |
R4-2014308 |
Clarification of additional spurious emission requirements on two bands uplink Inter-band CA(R16) |
SoftBank Corp. |
R4-2014402 |
CR for TS38.101-1 Rel-15, Correction for definition of P-MPR |
CATT |
R4-2014403 |
CR for TS38.101-1 Rel-16, Correction for definition of P-MPR |
CATT |
R4-2014718 |
CR to TS38.101-1 on DC location correction |
Samsung |
R4-2014719 |
CR to TS38.101-1 on DC location correction |
Samsung |
R4-2014898 |
Coexistence cleanup for 38.101-1 Rel15 |
Apple Inc. |
R4-2014905 |
CR for TS 38.101-1: Correction to FR1 time mask for SRS antenna switching |
Apple Inc. |
R4-2014906 |
CR for TS 38.101-1: Correction to FR1 time mask for SRS antenna switching |
Apple Inc. |
R4-2015998 |
Correction to spurious co-existence requirements for n28 and n83 |
Keysight Technologies UK Ltd |
R4-2016470 |
CR for TS 38.101-3: correction CR for simultaneous Tx/Rx operation (R15) |
Huawei, HiSilicon |
R4-2016471 |
CR for TS 38.101-1: correction CR for simultaneous Tx/Rx operation (R16) |
Huawei, HiSilicon |
R4-2016490 |
CR for TS 38.101-1: correction of delta Tib for UE supporting multiple band combinations (R15) |
Huawei, HiSilicon |
R4-2016491 |
CR for TS 38.101-1: correction of delta Tib for UE supporting multiple band combinations (R16) |
Huawei, HiSilicon |
R4-2016494 |
Update of configured transmitted power to remove ambiguity in TL,C (Rel-15) |
Huawei, HiSilicon |
R4-2016495 |
Update of configured transmitted power to remove ambiguity in TL,C (Rel-16) |
Huawei, HiSilicon |
R4-2016521 |
CR for TS 38.101-1 Pcmax |
Huawei, HiSilicon |
R4-2016522 |
CR on TS 38.101-1 Pcmax |
Huawei, HiSilicon |
R4-2016531 |
on 5MHz AMPR for NS_38 |
Huawei, HiSilicon |
R4-2016534 |
CR on correction for AMPR NS_38,NS_40 and NS_41 |
Huawei, HiSilicon |
R4-2016535 |
CR for 38.101-1 on corrections for AMPR-Rel-16 |
Huawei, HiSilicon |
R4-2016569 |
EVM Measurement for 2-Layer Uplink MIMO |
Lenovo, Motorola Mobility |
R4-2016578 |
CR to DMRS position in UL RMC for FR1 |
Qualcomm Incorporated |
R4-2016780 |
CR to 38.101-1: UL MIMO EVM and emission requirements update |
Qualcomm Incorporated |
R4-2016781 |
CR to TS38.101-1 on DC location correction |
Samsung |
R4-2016782 |
CR on correction for AMPR NS_38,NS_40 and NS_41 |
Huawei, HiSilicon |
R4-2016783 |
CR to DMRS position in UL RMC for FR1 |
Qualcomm Incorporated |
R4-2016993 |
CR to DMRS position in UL RMC for FR1 |
Qualcomm Incorporated |
4.2.1.2 |
Maintenance for Receiver characteristics [NR_newRAT-Core] |
|
R4-2015016 |
CR to TS 38.101-1[R15]: Clarification of non-simultaneous Rx/Tx operation for CA_n77-n79 and CA_n78-n79 in TS 38.101-1. |
NTT DOCOMO, INC. |
R4-2015017 |
CR to TS 38.101-1[R16]: Clarification of non-simultaneous Rx/Tx operation for CA_n77-n79 and CA_n78-n79 in TS 38.101-1. |
NTT DOCOMO, INC. |
R4-2015029 |
CR to TS 38.101-1: Correction on applicability of 4Rx requirements for CA |
ZTE Corporation |
R4-2015030 |
CR to TS 38.101-1: Correction on applicability of 4Rx requirements for CA |
ZTE Corporation |
R4-2015558 |
Discussion and reply draft LS on structure of NR CA reference sensitivity requirements in 38.101-1 |
Huawei, HiSilicon |
R4-2015559 |
CR for 38.101-1 to adjust the structure of NR CA REFSENS |
Huawei, HiSilicon |
R4-2015560 |
CR for 38.101-1 to adjust the structure of NR CA REFSENS (Rel-16) |
Huawei, HiSilicon |
R4-2016789 |
CR to TS 38.101-1[R15]: Clarification of non-simultaneous Rx/Tx operation for CA_n77-n79 and CA_n78-n79 in TS 38.101-1. |
NTT DOCOMO, INC. |
4.2.2 |
[FR2] Maintenance for 38.101-2 [NR_newRAT-Core] |
|
R4-2016053 |
Frequency separation class alignment |
Ericsson |
R4-2016605 |
Email discussion summary for [97e][103] NR_NewRAT_UE_RF_Part_2 |
Moderator (Apple) |
R4-2016947 |
Email discussion summary for [97e][103] NR_NewRAT_UE_RF_Part_2 |
Moderator (Apple) |
R4-2016994 |
WF on NR SCC UL power drop behavior in FR2 |
Ericsson |
4.2.2.1 |
Regulatory Tx/Rx spurious emission limits handling [NR_newRAT-Core] |
|
R4-2014054 |
EESS protection related requirements for FR2 bands |
Nokia, Nokia Shanghai Bell |
R4-2014055 |
EESS protection related requirements for FR2 bands |
Nokia, Nokia Shanghai Bell |
R4-2014257 |
draft LS to RAN5 on new emissions requirements |
Qualcomm Incorporated |
R4-2014258 |
On introduction of new emissions requirements to existing bands |
Qualcomm Incorporated |
R4-2014259 |
CR to 38.101-2: Introduction of NS_203 |
Qualcomm Incorporated |
R4-2014260 |
CR to 38.101-2: Introduction of NS_203 |
Qualcomm Incorporated |
R4-2014885 |
CR for introduction of EESS protection applied after 2021 |
NTT DOCOMO INC. |
R4-2014886 |
CR for introduction of EESS protection applied after 2021 |
NTT DOCOMO INC. |
R4-2014925 |
Further consideration on EESS protection |
NTT DOCOMO INC. |
R4-2014926 |
Further consideration on EESS protection |
NTT DOCOMO INC. |
R4-2015211 |
Remaining issues on WRC-19 |
Nokia, Nokia Shanghai Bell |
R4-2015255 |
on FR2 spurious emission NS handling |
Xiaomi |
R4-2016532 |
on FR2 EESS protection emission requirement |
Huawei, HiSilicon |
R4-2016785 |
EESS protection related requirements for FR2 bands |
Nokia, Nokia Shanghai Bell |
4.2.2.2 |
Maintenance for Transmitter characteristics [NR_newRAT-Core] |
|
R4-2014261 |
CR to 38.101-2: ULCA clarifications |
Qualcomm Incorporated |
R4-2014262 |
CR to 38.101-2: ULCA clarifications |
Qualcomm Incorporated |
R4-2014404 |
CR for TS38.101-2 Rel-15, Correction for definition of P-MPR |
CATT |
R4-2014405 |
CR for TS38.101-2 Rel-16, Correction for definition of P-MPR |
CATT |
R4-2014684 |
Transmission gap for relative power tolerance in FR2 |
Anritsu corporation |
R4-2014685 |
Transmission gap for relative power tolerance in FR2 |
Anritsu corporation |
R4-2014711 |
PCC SCC prioritization issue solution |
Qualcomm Incorporated |
R4-2014720 |
CR to TS38.101-2 on DC location correction |
Samsung |
R4-2014721 |
CR to TS38.101-2 on DC location correction |
Samsung |
R4-2014907 |
CR for TS 38.101-2: Clarification for NS_202 emission requirements |
Apple Inc. |
R4-2014908 |
CR for TS 38.101-2: Clarification for NS_202 |
Apple Inc. |
R4-2015334 |
Discussion on FR2 equal PSD in CA and draft LS |
OPPO |
R4-2015335 |
CR on FR2 equal PSD in UL CA |
OPPO |
R4-2015970 |
Correction to Pcmax: total radiated power |
Ericsson |
R4-2015971 |
Correction to Pcmax: total radiated power |
Ericsson |
R4-2016056 |
Correction of transmission gap definition for Relative power tolerance |
Ericsson |
R4-2016057 |
Correction of transmission gap definition for Relative power tolerance |
Ericsson |
R4-2016459 |
CR for 38.101-2: IBB and ACS corrections |
T-Mobile USA |
R4-2016460 |
Mirror CR for 38.101-2: IBB and ACS corrections |
T-Mobile USA |
R4-2016579 |
CR to DMRS position in UL RMC for FR2 |
Qualcomm Incorporated |
R4-2016786 |
CR to TS38.101-2 on DC location correction |
Samsung |
R4-2016787 |
CR to DMRS position in UL RMC for FR2 |
Qualcomm Incorporated |
R4-2017823 |
CR to DMRS position in UL RMC for FR2 |
Qualcomm Incorporated |
4.2.2.3 |
Maintenance for Receiver characteristics [NR_newRAT-Core] |
|
R4-2016031 |
Correction to EIS definition |
Rohde & Schwarz |
R4-2016032 |
Correction to EIS definition |
Rohde & Schwarz |
R4-2016499 |
CR to 38.101-2: Frequency separation class update |
Qualcomm Incorporated |
R4-2016520 |
CR on FR2 intra-band NC DL CA refsens |
Huawei, HiSilicon |
R4-2016545 |
draft LS to RAN2 on Rel-15 frequency separation class update |
Qualcomm Incorporated |
R4-2016590 |
CR for intra-band NC DL CA Rrefsens |
Huawei, HiSilicon |
R4-2016788 |
Correction to EIS definition |
Rohde & Schwarz |
4.2.3 |
Maintenance for 38.101-3 [NR_newRAT-Core] |
|
R4-2014914 |
CR for TS 38.101-3: Corrections for intra-band contiguous EN-DC configurations |
Apple Inc. |
R4-2016238 |
CR 38101-3 R15 Band 10 protection and DC_42_n79 correction |
Skyworks Solutions Inc. |
R4-2016241 |
CR 38101-3 R16 Band 10 protection and DC_42_n79 correction |
Skyworks Solutions Inc. |
R4-2016606 |
Email discussion summary for [97e][104] NR_NewRAT_UE_RF_Part_3 |
Moderator (Huawei) |
R4-2016790 |
CR 38101-3 R15 Band 10 protection and DC_42_n79 correction |
Skyworks Solutions Inc. |
R4-2016948 |
Email discussion summary for [97e][104] NR_NewRAT_UE_RF_Part_3 |
Moderator (Huawei) |
R4-2016988 |
LS to RAN2 on UE simultaneous Rx/Tx capability |
RAN4 |
4.2.3.1 |
[FR1] Maintenance for Transmitter characteristics within FR1 [NR_newRAT-Core] |
|
R4-2014309 |
Clarification of additional spurious emission requirements on Inter-band EN-DC(R15) |
SoftBank Corp. |
R4-2014310 |
Clarification of additional spurious emission requirements on Inter-band EN-DC(R16) |
SoftBank Corp. |
R4-2014900 |
Coexistence cleanup for 38.101-3 Rel15 |
Apple Inc. |
R4-2014917 |
LS response on simultaneous Rx/Tx for inter-band NR-DC |
Apple Inc. |
R4-2015337 |
CR on simultaneous Tx-Rx for EN-DC |
OPPO |
R4-2015338 |
CR on simultaneous Tx-Rx for EN-DC (R16 mirror CR) |
OPPO |
R4-2015805 |
Correction of CR0325 implementation |
ETSI MCC |
R4-2015992 |
CR to TS 38.101-3 clarifications on indication of Single Uplink allowed for intra-band EN-DC and NE-DC |
CHTTL |
R4-2015999 |
CR to TS 38.101-3 clarifications on indication of Single Uplink allowed for intra-band EN-DC and NE-DC |
CHTTL |
R4-2016001 |
Draft reply LS on simultaneous Rx/Tx for inter-band NR-DC |
ZTE Wistron Telecom AB |
R4-2016054 |
Correction of p-Max I.E and corresponding references |
Ericsson |
R4-2016055 |
Correction of p-Max I.E and corresponding references |
Ericsson |
R4-2016469 |
On simultaneous Rx/Tx UE capability |
Huawei, HiSilicon |
R4-2016472 |
CR for TS 38.101-3: correction CR for simultaneous Tx/Rx operation (R15) |
Huawei, HiSilicon |
R4-2016473 |
CR for TS 38.101-3: correction CR for simultaneous Tx/Rx operation (R16) |
Huawei, HiSilicon |
R4-2016482 |
CR for TS 38.101-3: correction of power class for EN-DC |
Huawei, HiSilicon |
R4-2016485 |
CR for 38.101-3 Correction on EN-DC synchronous carriers (R15) |
Huawei, HiSilicon |
R4-2016486 |
CR for 38.101-3 Correction on EN-DC synchronous carriers (R16) |
Huawei, HiSilicon |
R4-2016492 |
CR for TS 38.101-3: correction of delta Tib for UE supporting multiple band combinations (R15) |
Huawei, HiSilicon |
R4-2016493 |
CR for TS 38.101-3: correction of delta Tib for UE supporting multiple band combinations (R16) |
Huawei, HiSilicon |
R4-2016496 |
CR for TS 38.101-3: correction of spurious emission band UE co-existence (R15) |
Huawei, HiSilicon |
R4-2016497 |
CR for TS 38.101-3: correction of spurious emission band UE co-existence (R16) |
Huawei, HiSilicon |
R4-2016498 |
Adding delta TIB requirement for DC_2-7-7-13_n66 |
Huawei, HiSilicon |
R4-2016595 |
on UE capability for intra-band ENDC and LS to RAN2 |
Huawei, HiSilicon |
R4-2016791 |
CR for TS 38.101-3: correction of spurious emission band UE co-existence (R15) |
Huawei, HiSilicon |
R4-2016792 |
Correction of p-Max I.E and corresponding references |
Ericsson |
R4-2016793 |
Correction of p-Max I.E and corresponding references |
Ericsson |
R4-2016794 |
CR for 38.101-3 Correction on EN-DC synchronous carriers (R15) |
Huawei, HiSilicon |
R4-2016844 |
Adding delta TIB requirement for DC_2-7-7-13_n66 |
Huawei, HiSilicon |
R4-2017816 |
CR for TS 38.101-3: correction of spurious emission band UE co-existence (R16) |
Huawei, HiSilicon |
R4-2017821 |
CR to TS 38.101-3 clarifications on indication of Single Uplink allowed for intra-band EN-DC and NE-DC |
CHTTL |
4.2.3.2 |
[FR1+FR2] Maintenance for Transmitter characteristics involving both FR1 and FR2 [NR_newRAT-Core] |
|
R4-2015034 |
CR to TS 38.101-3: Some corrections on the ENDC |
ZTE Corporation |
R4-2015035 |
CR to TS 38.101-3: Some corrections on the ENDC |
ZTE Corporation |
R4-2016991 |
CR to TS 38.101-3: Some corrections on the ENDC |
ZTE Corporation |
4.2.3.3 |
[FR1] Maintenance for Receiver characteristics within FR1 [NR_newRAT-Core] |
|
R4-2014165 |
CR CatF Cross Band Noise DC_1_n40_highBW |
Qualcomm |
R4-2014166 |
CR CatA Cross Band Noise DC_1_n40_hignBW |
Qualcomm |
R4-2014682 |
UL output power for spurious response and general Rx |
Anritsu corporation, Apple Inc. |
R4-2014683 |
UL output power for spurious response and general Rx |
Anritsu corporation, Apple Inc. |
R4-2015796 |
CR to correct MSD of DC_1A-41A_n77A |
KDDI Corporation |
R4-2015797 |
CR to correct MSD of DC_1A-41A_n77A |
KDDI Corporation |
R4-2016085 |
CR to 38.101-3 DC_1A-20A_n28A Missing MSD |
VODAFONE Group Plc |
R4-2016087 |
CR to 38.101-3 DC_1A-20A_n28A Missing MSD |
VODAFONE Group Plc |
R4-2016225 |
Correction of applicability of 2Rx requirements |
vivo |
R4-2016226 |
CR to TS38.101-3[R16] Applicability of 2Rx requirements |
vivo |
R4-2016990 |
Correction of applicability of 2Rx requirements |
vivo |
R4-2017826 |
CR to TS38.101-3[R16] Applicability of 2Rx requirements |
vivo |
4.4.1 |
General [NR_newRAT-Core] |
|
R4-2014313 |
Support of Japan regulation for 2.5 GHz(BWA) in NR BS |
SoftBank Corp., KDDI Corporation, NEC Corporation |
R4-2017400 |
Email discussion summary for [97e][302] NR_BSRF_Maintenance |
Moderator (Ericsson) |
R4-2017602 |
Email discussion summary for [97e][302] NR_BSRF_Maintenance |
Moderator (Ericsson) |
4.4.2 |
Transmitter characteristics maintenance [NR_newRAT-Core] |
|
R4-2016345 |
CR to 38.104 on Category B OTA spurious emissions for Band n257 |
Ericsson |
R4-2016346 |
CR to 38.104 on Category B OTA spurious emissions for and n257 |
Ericsson |
R4-2016347 |
CR to 38.141-2 on Category B OTA spurious emissions for Band n257 |
Ericsson |
R4-2016348 |
CR to 38.141-2 on Category B OTA spurious emissions for Band n257 |
Ericsson |
4.5.1 |
General [NR_newRAT-Perf] |
|
R4-2017401 |
Email discussion summary for [97e][303] NR_Conformance_Maintenance |
Moderator (Huawei) |
R4-2017586 |
WF on AAS co-location for adjacent bands |
Huawei |
R4-2017603 |
Email discussion summary for [97e][303] NR_Conformance_Maintenance |
Moderator (Huawei) |
R4-2017679 |
Email discussion summary for [97e][303] NR_Conformance_Maintenance |
Moderator (Huawei) |
R4-2017697 |
Email discussion summary for [97e][303] NR_Conformance_Maintenance |
Moderator (Huawei) |
4.5.2.1 |
eAAS specifications [NR_newRAT-Perf/Core] |
|
R4-2015949 |
CR to TS 37.145-1: correction of manufacturer |
Huawei |
R4-2015950 |
CR to TS 37.145-1: correction of manufacturer |
Huawei |
R4-2015951 |
CR to TS 37.145-1: correction of manufacturer |
Huawei |
R4-2015952 |
CR to TS 37.145-1: correction of manufacturer |
Huawei |
R4-2015953 |
CR to TS 37.145-2: correction of manufacturer |
Huawei |
R4-2015954 |
CR to TS 37.145-2: correction of manufacturer |
Huawei |
R4-2015955 |
CR to TS 37.145-2: correction of manufacturer |
Huawei |
R4-2015956 |
CR to TS 37.145-2: correction of manufacturer |
Huawei |
R4-2016068 |
CR to TS 37.145-2 - Update CLTA definition, Rel-15 |
Huawei |
R4-2016069 |
CR to TS 37.145-2 - Update CLTA definition, Rel-16 |
Huawei |
R4-2016073 |
CR to TS 37.145-1: Corrections to conformance requirements, Rel-15 |
Huawei |
R4-2016074 |
CR to TS 37.145-1: Corrections to conformance requirements, Rel-16 |
Huawei |
R4-2016075 |
CR to TS 37.145-2: Corrections to conformance requirements including UEM additional requirements, Rel-15 |
Huawei |
R4-2016076 |
CR to TS 37.145-2: Corrections to conformance requirements including UEM additional requirements, Rel-16 |
Huawei |
R4-2016077 |
CR to TS 37.105: Corrections to core requirements including UEM additional requirements, Rel-15 |
Huawei |
R4-2016078 |
CR to TS 37.105: Corrections to core requirements including UEM additional requirements, Rel-16 |
Huawei |
R4-2016079 |
Discussion on AAS UEM additional requirements |
Huawei |
R4-2016080 |
CR to TS 37.145-2: Corrections to single RAT E-UTRA additional requirements for band 89, Rel-16 |
Huawei |
R4-2016127 |
CR to 37.145-2: Correction on NR REFSENS |
ZTE Corporation |
R4-2016128 |
CR to 37.145-2: Correction on NR REFSENS |
ZTE Corporation |
R4-2016202 |
CR to 37.145-1: Correction to applicability of additional BC3 requirement (Rel-15) |
Nokia, Nokia Shanghai Bell |
R4-2016203 |
CR to 37.145-1: Correction to applicability of additional BC3 requirement (Rel-16) |
Nokia, Nokia Shanghai Bell |
R4-2016204 |
CR to 37.145-2: Correction to applicability of additional BC3 requirement (Rel-15) |
Nokia, Nokia Shanghai Bell |
R4-2016205 |
CR to 37.145-2: Correction to applicability of additional BC3 requirement (Rel-16) |
Nokia, Nokia Shanghai Bell |
R4-2016282 |
CR to TS 37.145-2: Out-of-band co-location test antenna definition |
Nokia, Nokia Shanghai Bell |
R4-2016283 |
CR to TS 37.145-2: Out-of-band co-location test antenna definition |
Nokia, Nokia Shanghai Bell |
R4-2016502 |
TS 37.145-2: Corrections OTA SEM, OTA Rx intermod and OTA ACS |
Ericsson |
R4-2016503 |
TS 37.145-2: Corrections OTA SEM, OTA Rx intermod and OTA ACS |
Ericsson |
R4-2017588 |
CR to TS 37.145-2: Out-of-band co-location test antenna definition |
Nokia, Nokia Shanghai Bell |
R4-2017589 |
CR to TS 37.145-1: correction of manufacturer |
Huawei |
R4-2017590 |
CR to TS 37.145-1: Corrections to conformance requirements, Rel-15 |
Huawei |
R4-2017591 |
CR to TS 37.105: Corrections to core requirements including UEM additional requirements, Rel-15 |
Huawei |
R4-2017649 |
CR to TS 37.145-2: correction of manufacturer |
Huawei |
R4-2017662 |
CR to TS 37.145-2: Corrections to conformance requirements including UEM additional requirements, Rel-15 |
Huawei |
4.5.2.2 |
MSR specifications [NR_newRAT-Perf/Core] |
|
R4-2015957 |
CR to TS 37.104: addition of missing note for BC1/BC3 OBUE applicability table for WA BS, Rel-16 |
Huawei |
R4-2016184 |
CR to 37.104: Correction to ACLR limit in non-contiguous spectrum (Rel-15) |
Nokia, Nokia Shanghai Bell |
R4-2016185 |
CR to 37.104: Correction to ACLR limit in non-contiguous spectrum (Rel-16) |
Nokia, Nokia Shanghai Bell |
R4-2016186 |
CR to 37.141: Correction to ACLR limit in non-contiguous spectrum (Rel-15) |
Nokia, Nokia Shanghai Bell |
R4-2016187 |
CR to 37.141: Correction to ACLR limit in non-contiguous spectrum (Rel-16) |
Nokia, Nokia Shanghai Bell |
R4-2016349 |
CR to 37.104 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016350 |
CR to 37.104 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016351 |
CR to 37.141 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016352 |
CR to 37.141 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016353 |
CR to 37.105 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016354 |
CR to 37.105 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016355 |
CR to 37.145-1 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016356 |
CR to 37.145-1 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016357 |
CR to 37.145-2 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016358 |
CR to 37.145-2 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016359 |
CR to 36.104 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016360 |
CR to 36.104 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016361 |
CR to 36.141 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016362 |
CR to 36.141 on Removal of additional limit for Band 1 |
Ericsson |
R4-2016363 |
CR to 37.104 on MSR Blocking correction |
Ericsson |
R4-2016364 |
CR to 37.104 on MSR Blocking correction |
Ericsson |
R4-2016365 |
CR to 37.141 on MSR Blocking correction |
Ericsson |
R4-2016366 |
CR to 37.141 on MSR Blocking correction |
Ericsson |
R4-2016367 |
CR to 37.105 on NR+UTRA support for AAS |
Ericsson |
R4-2016368 |
CR to 37.105 on NR+UTRA support for AAS |
Ericsson |
R4-2017430 |
CR to 37.105 on Removal of additional limit for Band 1 |
Ericsson |
R4-2017431 |
CR to 37.145-2 on Removal of additional limit for Band 1 |
Ericsson |
4.5.2.3 |
NR conformance testing specifications [NR_newRAT-Perf] |
|
R4-2015378 |
On PN23 sequence generation for data content for NR test models |
Nokia, Nokia Shanghai Bell |
R4-2015379 |
CR to TS 38.141-1 clarification on PN23 sequence generation |
Nokia, Nokia Shanghai Bell |
R4-2015380 |
CR to TS 38.141-1 clarification on PN23 sequence generation |
Nokia, Nokia Shanghai Bell |
R4-2015381 |
CR to TS 38.141-2 clarification on PN23 sequence generation |
Nokia, Nokia Shanghai Bell |
R4-2015382 |
CR to TS 38.141-2 clarification on PN23 sequence generation |
Nokia, Nokia Shanghai Bell |
R4-2016067 |
Discussion on CLTA maximum height |
Huawei |
R4-2016070 |
CR to TS 38.141-2 - Update CLTA definition, Rel-15 |
Huawei |
R4-2016071 |
CR to TS 38.141-2 - Update CLTA definition, Rel-16 |
Huawei |
R4-2016072 |
Discussion on co-location for adjacent bands |
Huawei |
R4-2016284 |
On selecting CLTA maximum height |
Nokia, Nokia Shanghai Bell |
R4-2016286 |
CR to TS 38.141-2: Out-of-band co-location test antenna definition |
Nokia, Nokia Shanghai Bell |
R4-2016287 |
CR to TS 38.141-2: Out-of-band co-location test antenna definition |
Nokia, Nokia Shanghai Bell |
4.5.4 |
Radiated conformance testing (38.141-2) [NR_newRAT-Perf] |
|
R4-2014394 |
Discussion on out of band CLTA maximum height |
CATT |
R4-2014395 |
CR for TS 38.141-2: Correction on half-power vertical beam width for the out of band CLTA |
CATT |
R4-2014396 |
CR for TS 38.141-2: Correction on half-power vertical beam width for the out of band CLTA |
CATT |
R4-2015716 |
CR to TS 38.141-2: Improvement of out-of-band CLTA characteristics |
Ericsson |
R4-2015717 |
CR to TS 38.141-2: Improvement of out-of-band CLTA characteristics |
Ericsson |
R4-2016152 |
CR to 38.141-2: Annex C correction on frequency range of FR2 TT table (C.2) |
Keysight Technologies UK Ltd |
R4-2016153 |
CR to 38.141-2: Annex C correction on frequency range of FR2 TT table (C.2) |
Keysight Technologies UK Ltd |
R4-2016289 |
Discussions on TRP procedures |
Nokia, Nokia Shanghai Bell |
R4-2017587 |
CR to TS 38.141-2: Improvement of out-of-band CLTA characteristics |
Ericsson |
R4-2017592 |
CR to 38.141-2: Annex C correction on frequency range of FR2 TT table (C.2) |
Keysight Technologies UK Ltd |
R4-2017655 |
CR to 38.141-2: Annex C correction on frequency range of FR2 TT table (C.2) |
Keysight Technologies UK Ltd |
4.6 |
BS EMC [NR_newRAT-Core] |
|
R4-2015958 |
CR to TS 38.113: correction of the scope and other technical improvements, Rel-15 |
Huawei |
R4-2015959 |
CR to TS 38.113: correction of the scope and other technical improvements, Rel-16 |
Huawei |
R4-2017402 |
Email discussion summary for [97e][304] NR_EMC |
Moderator (ZTE) |
R4-2017441 |
CR to TS 38.113: correction of the scope and other technical improvements, Rel-15 |
Huawei |
R4-2017604 |
Email discussion summary for [97e][304] NR_EMC |
Moderator (ZTE) |
4.6.1.2 |
Immunity requirements [NR_newRAT-Core] |
|
R4-2015568 |
CR to TS 38.113 correcting Exclusion Bands Title, Release 15 |
Ericsson Inc. |
R4-2015569 |
CR to TS 38.113 correcting Exclusion Bands Title, Release 16 |
Ericsson Inc. |
4.6.2 |
Performance requirements [NR_newRAT-Perf] |
|
R4-2015100 |
CR to TS 37.113 on Voltage dips and interruptions, Release 15 |
Ericsson |
R4-2015101 |
CR to TS 37.113 on Voltage dips and interruptions, Release 16 |
Ericsson |
R4-2015102 |
CR to TS 38.113 on Voltage dips and interruptions, Release 15 |
Ericsson |
R4-2015103 |
CR to TS 38.113 on Voltage dips and interruptions, Release 16 |
Ericsson |
R4-2015104 |
CR to TS 38.113 on Performance criteria for transient phenomena, Release 15 |
Ericsson |
R4-2015105 |
CR to TS 38.113 on Performance criteria for transient phenomena, Release 16 |
Ericsson |
R4-2017435 |
CR to TS 37.113 on Voltage dips and interruptions, Release 15 |
Ericsson |
R4-2017436 |
CR to TS 37.113 on Voltage dips and interruptions, Release 16 |
Ericsson |
R4-2017437 |
CR to TS 38.113 on Voltage dips and interruptions, Release 15 |
Ericsson |
R4-2017438 |
CR to TS 38.113 on Voltage dips and interruptions, Release 16 |
Ericsson |
R4-2017439 |
CR to TS 38.113 on Performance criteria for transient phenomena, Release 15 |
Ericsson |
R4-2017440 |
CR to TS 38.113 on Performance criteria for transient phenomena, Release 16 |
Ericsson |
4.7 |
RRM core requirements maintenance (38.133/36.133) [NR_newRAT-Core] |
|
R4-2014237 |
Discussion on RRC based BWP switch for Scell |
Apple |
R4-2014238 |
CR on Applicability of RRC based BWP switch requirements - Rel15 |
Apple |
R4-2014239 |
CR on Applicability of RRC based BWP switch requirements - Rel16 |
Apple |
R4-2014268 |
CR on CSI-RS BW condition for BFD/CBD R15 |
Apple |
R4-2014269 |
CR on CSI-RS BW condition for BFD/CBD R16 |
Apple |
R4-2014270 |
On AP-CSI-RS based L1-RSRP measurement |
Apple, Huawei, HiSilicon |
R4-2014271 |
CR on AP-CSI-RS based L1-RSRP measurement R15 |
Apple, Huawei, HiSilicon |
R4-2014272 |
CR on AP-CSI-RS based L1-RSRP measurement R16 |
Apple, Huawei, HiSilicon |
R4-2014273 |
On CSSF for R15 EN-DC |
Apple |
R4-2014274 |
CR on CSSF for R15 EN-DC |
Apple |
R4-2014565 |
Discussion of RRC based BWP switching on single CC |
Intel Corporation |
R4-2014693 |
CR on carrier frequency range of PCell/PSCell for the maximum number of RLM-RS resources |
CMCC |
R4-2014694 |
CR on carrier frequency range of PCell/PSCell for the maximum number of RLM-RS resources |
CMCC |
R4-2014760 |
Remaining issues on RRM in R15 |
MediaTek inc. |
R4-2014761 |
CR on active BWP switch in R15 |
MediaTek inc. |
R4-2014762 |
CR on active BWP switch in R16 |
MediaTek inc. |
R4-2014763 |
CR on active TCI state switching delay in R15 |
MediaTek inc. |
R4-2014764 |
CR on active TCI state switching delay in R16 |
MediaTek inc. |
R4-2014765 |
CR on MO merge in R15 |
MediaTek inc. |
R4-2014766 |
CR on MO merge in R16 |
MediaTek inc. |
R4-2015159 |
Addition of symbol definitions |
Ericsson |
R4-2015160 |
Addition of symbol definitions |
Ericsson |
R4-2015208 |
CR on BWP switch |
MediaTek inc. |
R4-2015209 |
CR on TCI state |
MediaTek inc. |
R4-2015210 |
CR on MO merge |
MediaTek inc. |
R4-2015300 |
CR to TS 38.133 on DCI based BWP switch requirements applicability |
NEC |
R4-2015306 |
CR to TS 38.133 on clarification of applicability of SCell activation requirements for unknown FR1 cell |
NEC |
R4-2015445 |
Correction to CSSF calculation R15 |
Huawei, HiSilicon |
R4-2015446 |
Correction to CSSF calculation R16 |
Huawei, HiSilicon |
R4-2015527 |
CR on BFD and CBD requirements |
Huawei, HiSilicon |
R4-2015528 |
CR on BFD and CBD requirements_R16 |
Huawei, HiSilicon |
R4-2015529 |
CR on RRC-based BWP switch requirements |
Huawei, HiSilicon |
R4-2015530 |
CR on RRC-based BWP switch requirements_R16 |
Huawei, HiSilicon |
R4-2015570 |
CR to 38.133: Correction to SCell activation delay requirements |
ZTE |
R4-2015571 |
CR to 38.133 correction to SCell activation delay requirements |
ZTE |
R4-2015572 |
CR to 38.133: Correction to RRC based BWP switch requirements |
ZTE |
R4-2015573 |
CR to 38.133 correction to RRC based BWP switch requirements |
ZTE |
R4-2015672 |
[CR] Specify RRC processing delay in TCI state switching delay |
ZTE Corporation |
R4-2015673 |
[CR] Specify RRC processing delay in TCI state switching delay (Cat A) |
ZTE Corporation |
R4-2015731 |
CR to remove intra-frequency ECID requirements for NE-DC 36133 R15 |
Huawei, HiSilicon |
R4-2015732 |
CR to remove intra-frequency ECID requirements for NE-DC 36133 R16 |
Huawei, HiSilicon |
R4-2015733 |
CR to remove inter-RAT ECID requirements for NE-DC 38133 R15 |
Huawei, HiSilicon |
R4-2015734 |
CR to remove inter-RAT ECID requirements for NE-DC 38133 R16 |
Huawei, HiSilicon |
R4-2015735 |
Discussion on remaining issues in Rel-15 SCell activation requirements |
Huawei, HiSilicon |
R4-2015736 |
CR on SCell activation requirements R15 |
Huawei, HiSilicon |
R4-2015737 |
CR on SCell activation requirements R16 |
Huawei, HiSilicon |
R4-2015876 |
Introducing reference to the source of the Lmax and NRLM. |
Nokia, Nokia Shanghai Bell |
R4-2015877 |
Introducing reference to the source of the Lmax and NRLM. |
Nokia, Nokia Shanghai Bell |
R4-2016022 |
CR 36.133 Removal of brackets for SFTD measurements |
Ericsson |
R4-2016023 |
CR 36.133 Removal of brackets for SFTD measurements (Rel-16) |
Ericsson |
R4-2016162 |
HARQ delay during RRC based BWP, CBW and TCI switching procedures |
Ericsson |
R4-2016373 |
CR to 38.133 on Active BWP switch and Active TCI State Switching requirements - Rel15 |
Apple |
R4-2016374 |
CR to 38.133 on Active BWP switch and Active TCI State Switching requirements - Rel16 |
Apple |
R4-2016580 |
CR to TCI activation in FR1 |
Qualcomm Incorporated |
R4-2016581 |
CR to SSB-less SCell activation delay requirement for deactivated FR1 SCell |
Qualcomm Incorporated |
R4-2017000 |
Email discussion summary for [97e][201] NR_NewRAT_RRM_Core |
Moderator (Huawei) |
R4-2017034 |
Correction to CSSF calculation R15 |
Huawei, HiSilicon |
R4-2017035 |
WF on SSB-less SCell activation delay requirement |
Qualcomm |
R4-2017036 |
CR on SCell activation requirements R15 |
Huawei, HiSilicon |
R4-2017037 |
CR on CSI-RS BW condition for BFD/CBD R15 |
Apple |
R4-2017038 |
CR on AP-CSI-RS based L1-RSRP measurement R15 |
Apple, Huawei, HiSilicon |
R4-2017039 |
WF on RRC based BWP switching for SCell |
Apple |
R4-2017040 |
LS on RRC based BWP switching for SCell |
RAN4 |
R4-2017041 |
CR to 38.133 on Active BWP switch and Active TCI State Switching requirements - Rel15 |
Apple |
R4-2017271 |
Email discussion summary for [97e][201] NR_NewRAT_RRM_Core |
Moderator (Huawei) |
R4-2017307 |
CR to SSB-less SCell activation delay requirement for deactivated FR1 SCell |
Qualcomm |
R4-2017331 |
WF on CSSF calculation for Inter-RAT MO |
Huawei, HiSilicon |
R4-2017335 |
CR to TS 38.133 on DCI based BWP switch requirements applicability |
NEC |
R4-2017336 |
CR on MO merge in R15 |
MediaTek inc. |
R4-2017338 |
Introducing reference to the source of the Lmax and NRLM. |
Nokia, Nokia Shanghai Bell |
R4-2017342 |
CR on RRC-based BWP switch requirements |
Huawei, HiSilicon |
R4-2017343 |
CR to remove intra-frequency ECID requirements for NE-DC 36133 R15 |
Huawei, HiSilicon |
R4-2017344 |
CR to remove inter-RAT ECID requirements for NE-DC 38133 R15 |
Huawei, HiSilicon |
R4-2017377 |
CR to 38.133 on Active BWP switch and Active TCI State Switching requirements - Rel15 |
Apple |
R4-2017380 |
CR to 38.133 on Active BWP switch and Active TCI State Switching requirements - Rel16 |
Apple |
4.8 |
RRM perf. requirements maintenance (38.133/36.133) [NR_newRAT-Perf] |
|
R4-2014017 |
RB allocation and Noc level in RLM Test cases |
ANRITSU LTD |
R4-2014018 |
RB allocation and Noc level in RLM Test cases |
ANRITSU LTD |
R4-2014019 |
Update FR2 event-triggered reporting Test cases in A.5.6, A.7.6 |
ANRITSU LTD |
R4-2014020 |
Update FR2 event-triggered reporting Test cases in A.5.6, A.7.6 |
ANRITSU LTD |
R4-2014021 |
240kHz SSB SCS Configuration for FR2 SS-RSRP Test cases |
ANRITSU LTD |
R4-2014022 |
240kHz SSB SCS Configuration for FR2 SS-RSRP Test cases |
ANRITSU LTD |
R4-2014023 |
Correct UE beam assumption for Test Cases in A.5.6 |
ANRITSU LTD |
R4-2014024 |
Correct UE beam assumption for Test Cases in A.5.6 |
ANRITSU LTD |
R4-2014025 |
Modification of AG level in CORESET for RMC scheduling |
ANRITSU LTD |
R4-2014026 |
Aggregation level of CORESET for RMC scheduling |
ANRITSU LTD |
R4-2014027 |
Aggregation level of CORESET for RMC scheduling |
ANRITSU LTD |
R4-2014028 |
Clarify FR1 NSA SS-SINR measurement TCs |
ANRITSU LTD |
R4-2014029 |
Claify FR1 NSA SS-SINR measurement TCs |
ANRITSU LTD |
R4-2014046 |
FR1 Inter-frequency Event triggered Reporting tests in DRX |
ANRITSU LTD |
R4-2014047 |
FR1 Inter-frequency Event triggered Reporting tests in DRX |
ANRITSU LTD |
R4-2014048 |
E-UTRAN |
ANRITSU LTD |
R4-2014049 |
E-UTRAN |
ANRITSU LTD |
R4-2014181 |
[CR] NR Perf Maintenance R15 Cat F |
ZTE Corporation |
R4-2014182 |
[CR] NR Perf Maintenance R16 Cat A |
ZTE Corporation |
R4-2014183 |
[CR] NR Perf Maintenance R16 Cat F |
ZTE Corporation |
R4-2014231 |
Maintenance CR on SA inter-frequency event triggered reporting tests for FR1 |
Apple |
R4-2014372 |
CR on TS38.133 for cell activation and deactivation test case |
MediaTek inc. |
R4-2014373 |
CR on TS38.133 for cell activation and deactivation test case |
MediaTek inc. |
R4-2014374 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2014375 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2014376 |
Correction of active BWP switch test case |
MediaTek inc. |
R4-2014377 |
CR on TS38.133 for active BWP switch test cases |
MediaTek inc. |
R4-2014406 |
CR for TS38.133 Rel-15, Correction for RRM core and test cases |
CATT |
R4-2014407 |
CR for TS38.133 Rel-16, Correction for RRM core and test cases |
CATT |
R4-2014591 |
Draft CR on correcting SSB and RACH configuration in CSI-RS based beam failure detection and link recovery tests |
Qualcomm CDMA Technologies |
R4-2014592 |
Draft CR on correcting SSB and RACH configuration in CSI-RS based beam failure detection and link recovery tests |
Qualcomm CDMA Technologies |
R4-2014601 |
CR on TS 38.133 for radio link monitoring test case R15 |
MediaTek inc. |
R4-2014602 |
CR on TS 38.133 for radio link monitoring test case R16 |
MediaTek inc. |
R4-2014865 |
Correction on beamFailureInstanceMaxCount for test case of availability restriction during FR2 BFR in R15 |
MediaTek inc. |
R4-2014866 |
Correction on beamFailureInstanceMaxCount for test cases of availability restriction during FR2 BFR in R16 |
MediaTek inc. |
R4-2014947 |
Correction of RRM tests |
Nokia, Nokia Shanghai Bell |
R4-2014948 |
Correction of RRM tests |
Nokia, Nokia Shanghai Bell |
R4-2015148 |
Correction of beam assumptions in interfrequency EN-DC FR1+FR2 tests |
Ericsson |
R4-2015149 |
Correction of beam assumptions in interfrequency EN-DC FR1+FR2 tests |
Ericsson |
R4-2015150 |
Correction of TBD values in EN-DC PSCell addition and release delay test |
Ericsson |
R4-2015151 |
Correction of TBD values in EN-DC PSCell addition and release delay test |
Ericsson |
R4-2015152 |
Correction to types of requirements in annex A |
Ericsson |
R4-2015153 |
Correction to types of requirements in annex A |
Ericsson |
R4-2015154 |
Corrections to frequency range in interfrequency measurement procedures tests |
Ericsson |
R4-2015155 |
Corrections to frequency range in interfrequency measurement procedures tests |
Ericsson |
R4-2015157 |
Correction on TBD values in FR1+FR2 interfrequency RSRP accuracy tests |
Ericsson |
R4-2015158 |
Correction on TBD values in FR1+FR2 interfrequency RSRP accuracy tests |
Ericsson |
R4-2015161 |
Correction of TBD value in Radio Link Monitoring Out-of-sync Tests for FR2 configured with CSI-RS-based RLM |
Ericsson |
R4-2015162 |
Correction of TBD value in Radio Link Monitoring Out-of-sync Tests for FR2 configured with CSI-RS-based RLM |
Ericsson |
R4-2015163 |
Square bracket removal in 38.133 section A.1 to A.5 |
Ericsson |
R4-2015164 |
Square bracket removal in 38.133 section A.1 to A.5 |
Ericsson |
R4-2015165 |
Square bracket removal in 38.133 section A.6 to A.8 |
Ericsson |
R4-2015166 |
Square bracket removal in 38.133 section A.6 to A.8 |
Ericsson |
R4-2015447 |
Correction to CSI-RS RMC configuration R15 |
Huawei, HiSilicon |
R4-2015448 |
Correction to CSI-RS RMC configuration R16 |
Huawei, HiSilicon |
R4-2015449 |
Correction to cell reselection test cases R15 |
Huawei, HiSilicon |
R4-2015450 |
Correction to cell reselection test cases R16 |
Huawei, HiSilicon |
R4-2015451 |
Correction to inter-RAT handover test cases R15 |
Huawei, HiSilicon |
R4-2015452 |
Correction to inter-RAT handover test cases R16 |
Huawei, HiSilicon |
R4-2015453 |
Correction to NR measurement under LTE SA test cases R15 |
Huawei, HiSilicon |
R4-2015454 |
Correction to NR measurement under LTE SA test cases R16 |
Huawei, HiSilicon |
R4-2015455 |
Correction to inter-RAT SFTD measurement test cases R15 |
Huawei, HiSilicon |
R4-2015456 |
Correction to inter-RAT SFTD measurement test cases R16 |
Huawei, HiSilicon |
R4-2015457 |
CR on maintaining antenna configurations in TS38.133 |
Huawei, HiSilicon |
R4-2015458 |
CR on maintaining Antenna configurations in TS38.133 R16 |
Huawei, HiSilicon |
R4-2015459 |
CR on maintaining BFD/CBD measurements test cases R15 |
Huawei, HiSilicon |
R4-2015460 |
CR on maintaining BFD/CBD measurements test cases in TS38.133 R16 |
Huawei, HiSilicon |
R4-2015503 |
Correction on SA inter-RAT measurement FR1 test case |
Huawei, HiSilicon |
R4-2015531 |
CR on RRC-based active TCI state switch test case Rel-15 |
Huawei, HiSilicon |
R4-2015532 |
CR on RRC-based active TCI state switch test case Rel-16 |
Huawei, HiSilicon |
R4-2015674 |
[CR] NR Perf Maintenance R15 Cat F |
ZTE Corporation |
R4-2015738 |
CR on FR2 unkown SCell activation test cases R15 |
Huawei, HiSilicon |
R4-2015739 |
CR on FR2 unkown SCell activation test cases R16 |
Huawei, HiSilicon |
R4-2015740 |
CR on BWP in L1-RSRP delay and accuracy test cases R15 |
Huawei, HiSilicon |
R4-2015741 |
CR on BWP in L1-RSRP delay and accuracy test cases R16 |
Huawei, HiSilicon |
R4-2015823 |
CR: Correction of CFRA test in FR2 SA |
Ericsson |
R4-2015993 |
CR to TS 38.133: Corrections to inter-RAT FR1 test cases (Rel-15) |
Rohde & Schwarz |
R4-2015994 |
CR to TS 38.133: Corrections to inter-RAT FR1 test cases (Rel-16) |
Rohde & Schwarz |
R4-2015995 |
CR to TS 38.133: Corrections to inter-RAT FR2 test cases (Rel-15) |
Rohde & Schwarz |
R4-2015996 |
CR to TS 38.133: Corrections to inter-RAT FR2 test cases (Rel-16) |
Rohde & Schwarz |
R4-2016024 |
CR 38.133 Corrections to test cases for TCI state switching |
Ericsson |
R4-2016025 |
CR 38.133 Correction to test case for TCI state switching (Rel-16) |
Ericsson |
R4-2016160 |
Removal of annex B.2.6 on one shot timing adjustment in 38.133 |
Ericsson |
R4-2016161 |
Removal of annex B.2.6 on one shot timing adjustment in 38.133 |
Ericsson |
R4-2016163 |
Correction to NR FR1 DL active BWP switch of Cell with non-DRX in SA (A.6.5.6.2.1) |
Ericsson |
R4-2016164 |
Correction to NR FR1 DL active BWP switch of Cell with non-DRX in SA (A.6.5.6.2.1) |
Ericsson |
R4-2016582 |
Missing TRS Configurations in Test Cases |
Qualcomm Incorporated |
R4-2017001 |
Email discussion summary for [97e][202] NR_NewRAT_RRM_Perf |
Moderator (Ericsson) |
R4-2017042 |
Aggregation level of CORESET for RMC scheduling |
ANRITSU LTD |
R4-2017043 |
Correction to CSI-RS RMC configuration R15 |
Huawei, HiSilicon |
R4-2017044 |
RB allocation and Noc level in RLM Test cases |
ANRITSU LTD |
R4-2017045 |
Correct UE beam assumption for Test Cases in A.5.6 |
ANRITSU LTD |
R4-2017046 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2017047 |
Correction of active BWP switch test case |
MediaTek inc. |
R4-2017048 |
CR on correcting SSB and RACH configuration in CSI-RS based beam failure detection and link recovery tests |
Qualcomm CDMA Technologies |
R4-2017049 |
Correction on beamFailureInstanceMaxCount for test case of availability restriction during FR2 BFR in R15 |
MediaTek inc. |
R4-2017050 |
Correction of TBD values in EN-DC PSCell addition and release delay test |
Ericsson |
R4-2017051 |
Corrections to frequency range in interfrequency measurement procedures tests |
Ericsson |
R4-2017052 |
Square bracket removal in 38.133 section A.1 to A.5 |
Ericsson |
R4-2017053 |
Correction to cell reselection test cases R15 |
Huawei, HiSilicon |
R4-2017054 |
Correction to inter-RAT handover test cases R15 |
Huawei, HiSilicon |
R4-2017055 |
Correction to NR measurement under LTE SA test cases R15 |
Huawei, HiSilicon |
R4-2017056 |
Correction to inter-RAT SFTD measurement test cases R15 |
Huawei, HiSilicon |
R4-2017057 |
CR on RRC-based active TCI state switch test case Rel-15 |
Huawei, HiSilicon |
R4-2017058 |
[CR] NR Perf Maintenance R15 Cat F |
ZTE Corporation |
R4-2017059 |
CR to TS 38.133: Corrections to inter-RAT FR1 test cases (Rel-15) |
Rohde & Schwarz |
R4-2017060 |
CR to TS 38.133: Corrections to inter-RAT FR2 test cases (Rel-15) |
Rohde & Schwarz |
R4-2017061 |
Removal of annex B.2.6 on one shot timing adjustment in 38.133 |
Ericsson |
R4-2017162 |
CR on correcting SSB and RACH configuration in CSI-RS based beam failure detection and link recovery tests |
Qualcomm CDMA Technologies |
R4-2017163 |
Square bracket removal in 38.133 section A.6 to A.8 |
Ericsson |
R4-2017272 |
Email discussion summary for [97e][202] NR_NewRAT_RRM_Perf |
Moderator (Ericsson) |
R4-2017309 |
Correction to NR FR1 DL active BWP switch of Cell with non-DRX in SA (A.6.5.6.2.1) |
Ericsson |
R4-2017334 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2017368 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2017378 |
CR on TS38.133 for cell reselection test case |
MediaTek inc. |
R4-2017379 |
[CR] NR Perf Maintenance R16 Cat A |
ZTE Corporation |
4.9 |
Demodulation and CSI requirements maintenance (38.101-4/38.104) [NR_newRAT-Perf] |
|
R4-2017412 |
Email discussion summary for [97e][314] NR_Demod_Maintenance |
Moderator (Intel) |
R4-2017605 |
Email discussion summary for [97e][314] NR_Demod_Maintenance |
Moderator (Intel) |
4.9.1 |
UE demodulation requirements [NR_newRAT-Perf] |
|
R4-2014015 |
Update of Noc for NR operating bands in FR2 |
ANRITSU LTD |
R4-2014016 |
Update of Noc for NR operating bands in FR2 |
ANRITSU LTD |
R4-2015824 |
CR: Correction of FRC for PDSCH demodulation requirements |
Ericsson |
R4-2015825 |
CR: Correction of FRC for PDSCH demodulation requirements |
Ericsson |
R4-2016424 |
CR: Updates to OCNG pattern reference |
Huawei Technologies Sweden AB |
R4-2016425 |
CR: Updates OCNG pattern reference (Rel-16) |
Huawei Technologies Sweden AB |
R4-2016448 |
CR: Correction on OCNG pattern |
Qualcomm, Inc. |
R4-2016449 |
CR: Correction on OCNG pattern |
Qualcomm, Inc. |
R4-2017447 |
CR: Correction of FRC for PDSCH demodulation requirements |
Ericsson |
R4-2017448 |
CR: Updates to OCNG pattern reference |
Huawei Technologies Sweden AB |
R4-2017449 |
CR: Correction on OCNG pattern |
Qualcomm, Inc. |
R4-2017450 |
CR: Correction on OCNG pattern |
Qualcomm, Inc. |
4.9.2 |
CSI requirements [NR_newRAT-Perf] |
|
R4-2014050 |
Correction to FR1 Aperiodic CSI Reporting |
ANRITSU LTD |
R4-2014051 |
Correction to FR1 Aperiodic CSI Reporting |
ANRITSU LTD |
R4-2014052 |
Correction to FR2 PMI Aperiodic CSI Reporting |
ANRITSU LTD |
R4-2014053 |
Correction to FR2 PMI Aperiodic CSI Reporting |
ANRITSU LTD |
4.9.3 |
BS demodulation requirements [NR_newRAT-Perf] |
|
R4-2014494 |
CR for 38.141-2: Add error-free feedback in demodulation requirement test setup |
Nokia, Nokia Shanghai Bell |
R4-2014509 |
CR for 38.141-2: Add error-free feedback in demodulation requirement test setup |
Nokia, Nokia Shanghai Bell |
R4-2015843 |
Adding MCS12 and 30% throughput requirements and corresponding FRC tables for FR2 PUSCH performance in TS38.104 v15.11.0 |
Ericsson |
R4-2015844 |
Adding MCS12 and 30% throughput requirements and corresponding FRC tables for FR2 PUSCH performance in TS38.141-2 v15.7.0 |
Ericsson |
5.1 |
BS RF requirements [WI code or TEI] |
|
R4-2014469 |
CR to TS 36.141: Clarification on manufacturer |
Nokia, Nokia Shanghai Bell |
R4-2014470 |
CR to TS 36.141: Clarification on manufacturer |
Nokia, Nokia Shanghai Bell |
R4-2014471 |
CR to TS 36.141: Clarification on manufacturer |
Nokia, Nokia Shanghai Bell |
R4-2014472 |
CR to TS 36.141: Clarification on manufacturer |
Nokia, Nokia Shanghai Bell |
R4-2015375 |
Further discussion on additional optional EDT level for test |
Nokia, Nokia Shanghai Bell |
R4-2015376 |
CR to 37.107 with update of EDT level |
Nokia, Nokia Shanghai Bell |
R4-2015377 |
CR to 37.107 with update of EDT level |
Nokia, Nokia Shanghai Bell |
R4-2017399 |
Email discussion summary for [97e][301] LTE_BSRF_Maintenance |
Moderator (Ericsson) |
R4-2017451 |
CR to 37.107 with update of EDT level |
Nokia, Nokia Shanghai Bell |
R4-2017606 |
Email discussion summary for [97e][301] LTE_BSRF_Maintenance |
Moderator (Ericsson) |
5.2 |
UE RF requirements [WI code or TEI] |
|
R4-2014311 |
Clarifications and corrections on UE co-ex requirements(R15) |
SoftBank Corp. |
R4-2014312 |
Clarifications and corrections on UE co-ex requirements(R16) |
SoftBank Corp. |
R4-2014896 |
Coexistence cleanup for 36101 Rel15 |
Apple Inc. |
R4-2015549 |
CR for 36.101 to clarify the SCS supports for LTE MBMS (Rel-14) |
Huawei, HiSilicon |
R4-2015550 |
CR for 36.101 to clarify the SCS supports for LTE MBMS (Rel-15) |
Huawei, HiSilicon, ZTE |
R4-2015551 |
CR for 36.101 to clarify the SCS supports for LTE MBMS (Rel-16) |
Huawei, HiSilicon, ZTE |
R4-2015807 |
Test frequencies for NB-IOT UE in standalone operation |
Sony |
R4-2016035 |
CR Correction to B72 coex - CA_NS_08 - Band 10 protection 36.101 Rel15 |
Skyworks Solutions Inc. |
R4-2016607 |
Email discussion summary for [97e][105] LTE_Maintenance |
Moderator (Skyworks) |
R4-2016796 |
CR for 36.101 to clarify the SCS supports for LTE MBMS (Rel-14) |
Huawei, HiSilicon, ZTE |
R4-2016949 |
Email discussion summary for [97e][105] LTE_Maintenance |
Moderator (Skyworks) |
R4-2016996 |
CR Correction to B72 coex - CA_NS_08 - Band 10 protection 36.101 Rel15 |
Skyworks Solutions Inc. |
R4-2017830 |
Clarifications and corrections on UE co-ex requirements(R15) |
SoftBank Corp. |
R4-2017831 |
Clarifications and corrections on UE co-ex requirements(R16) |
SoftBank Corp. |
5.3 |
RRM requirements [WI code or TEI] |
|
R4-2015461 |
CR on maintaining V2X test cases in TS36.133 R14 |
Huawei, HiSilicon |
R4-2015462 |
CR on maintaining V2X test cases in TS36.133 R15 |
Huawei, HiSilicon |
R4-2015463 |
CR on maintaining V2X test cases in TS36.133 R16 |
Huawei, HiSilicon |
R4-2015838 |
CR: Correction of eMTC early-OOS/early-IS tests (Rel-14) |
Ericsson |
R4-2015839 |
CR: Correction of eMTC early-OOS/early-IS tests |
Ericsson |
R4-2015840 |
CR: Correction of eMTC early-OOS/early-IS tests |
Ericsson |
R4-2016012 |
CR 36.133 Corrections to test cases for SCell Hibernation |
Ericsson |
R4-2016013 |
CR 36.133 Correction to test cases for SCell Hibernation (Rel-16) |
Ericsson |
R4-2016548 |
Correction to test parameters for FDD and TDD intra-frequency RSRP for Cat-M1 UE in CEModeA |
Qualcomm Incorporated |
R4-2016549 |
Correction to test parameters for FDD and TDD intra-frequency RSRP for Cat-M1 UE in CEModeA |
Qualcomm Incorporated |
R4-2016550 |
Correction to test parameters for FDD and TDD intra-frequency RSRP for Cat-M1 UE in CEModeA |
Qualcomm Incorporated |
R4-2016551 |
Correction to test parameters for FDD and TDD intra-frequency RSRP for Cat-M1 UE in CEModeA |
Qualcomm Incorporated |
R4-2017002 |
Email discussion summary for [97e][203] LTE_RRM_maintenance |
Moderator (Ericsson) |
R4-2017063 |
CR on maintaining V2X test cases in TS36.133 R14 |
Huawei, HiSilicon |
R4-2017064 |
CR: Correction of eMTC early-OOS/early-IS tests (Rel-14) |
Ericsson |
R4-2017065 |
CR: Correction of eMTC early-OOS/early-IS tests |
Ericsson |
R4-2017066 |
Correction to test parameters for FDD and TDD intra-frequency RSRP for Cat-M1 UE in CEModeA |
Qualcomm Incorporated |
R4-2017273 |
Email discussion summary for [97e][203] LTE_RRM_maintenance |
Moderator (Ericsson) |
5.4.1 |
UE demodulation and CSI requirements [WI code or TEI] |
|
R4-2015589 |
CR on cleanup for LTE FeMBMS(Rel-14) |
Huawei, HiSilicon |
R4-2015590 |
CR on cleanup for LTE FeMBMS(Rel-15) |
Huawei, HiSilicon |
R4-2015591 |
CR on cleanup for LTE FeMBMS(Rel-16) |
Huawei, HiSilicon |
R4-2015630 |
CR: Updates to LTE V2X performance requirements |
Huawei, HiSilicon |
R4-2015668 |
CR for 36.101: Cleanup for performance requirements of sTTI (Rel-15) |
Huawei, HiSilicon |
R4-2015669 |
CR for 36.101: Cleanup for performance requirements of sTTI (Rel-16) |
Huawei, HiSilicon |
R4-2015835 |
CR: Addition of applicability for MTC UE capable of 64QAM DL |
Ericsson |
R4-2017411 |
Email discussion summary for [97e][313] LTE_Demod_Maintenance |
Moderator (Huawei) |
R4-2017452 |
CR on cleanup for LTE FeMBMS(Rel-14) |
Huawei, HiSilicon |
R4-2017453 |
CR on cleanup for LTE FeMBMS(Rel-15) |
Huawei, HiSilicon |
R4-2017454 |
CR on cleanup for LTE FeMBMS(Rel-16) |
Huawei, HiSilicon |
R4-2017455 |
CR for 36.101: Cleanup for performance requirements of sTTI (Rel-15) |
Huawei, HiSilicon |
R4-2017456 |
CR for 36.101: Cleanup for performance requirements of sTTI (Rel-16) |
Huawei, HiSilicon |
R4-2017607 |
Email discussion summary for [97e][313] LTE_Demod_Maintenance |
Moderator (Huawei) |
R4-2017645 |
CR: Updates to LTE V2X performance requirements |
Huawei, HiSilicon |
R4-2017646 |
CR: Updates to LTE V2X performance requirements |
Huawei, HiSilicon |
R4-2017656 |
CR: Updates to LTE V2X performance requirements |
Huawei, HiSilicon |
R4-2017657 |
CR: Updates to LTE V2X performance requirements |
Huawei, HiSilicon |
R4-2017680 |
CR for 36.101: Cleanup for performance requirements of sTTI (Rel-16) |
Huawei, HiSilicon |
5.4.2 |
BS demodulation requirements [WI code or TEI] |
|
R4-2014944 |
Correction of eLAA FRC table |
Nokia, Nokia Shanghai Bell |
R4-2014945 |
Correction of eLAA FRC table |
Nokia, Nokia Shanghai Bell |
R4-2014946 |
Correction of eLAA FRC table |
Nokia, Nokia Shanghai Bell |
6.1.2 |
RRM core requirements maintenance [LTE_eMTC5-Core] |
|
R4-2015778 |
[LS] Discussion on remaining issues in RSS measurement and eMTC in RRC_Inactive state |
Huawei, HiSilicon |
R4-2015779 |
CR on RSS measurement requirements |
Huawei, HiSilicon |
R4-2015780 |
CR to introduce measurement requirements for eMTC in RRC_Inactive |
Huawei, HiSilicon |
R4-2016141 |
Discussions on measurement requirement for eMTC UE in RRC_INACTIVE |
Ericsson |
R4-2016142 |
Measurement requirement for eMTC UE in RRC_INACTIVE |
Ericsson |
R4-2016143 |
Corrections to RSS based measurement requirements |
Ericsson |
R4-2016547 |
RRM requirements for eMTC UE in RRC_INACTIVE state |
Qualcomm Incorporated |
R4-2016587 |
Correction to RSS based measurement requirements |
Nokia, Nokia Shanghai Bell |
R4-2017024 |
Email discussion summary for [97e][225] LTE_eMTC5_RRM |
Moderator (Ericsson) |
R4-2017068 |
CR on RSS measurement requirements |
Huawei, HiSilicon |
R4-2017069 |
CR to introduce measurement requirements for eMTC in RRC_Inactive |
Huawei, HiSilicon |
R4-2017070 |
Correction to RSS based measurement requirements |
Nokia, Nokia Shanghai Bell, Ericsson |
R4-2017295 |
Email discussion summary for [97e][225] LTE_eMTC5_RRM |
Moderator (Ericsson) |
6.1.3 |
RRM perf. requirements [LTE_eMTC5-Perf] |
|
R4-2017071 |
Big CR: Introduction of Rel-16 eMTC RRM performance requirements (TS 36.133) |
Ericsson |
6.1.3.2 |
Test cases [LTE_eMTC5-Perf] |
|
R4-2015781 |
draftCR to introduce RSS related test cases |
Huawei, HiSilicon |
R4-2015841 |
Test cases of RLM for MPDCCH performance improvement |
Ericsson |
R4-2015842 |
Draft CR: Test cases of RLM for MPDCCH performance improvement |
Ericsson |
R4-2016144 |
Discussions on testing serving cell measurement relaxation requirements |
Ericsson |
R4-2016145 |
Test case on serving cell relaxation for eMTC |
Ericsson |
R4-2016552 |
Test cases for DL channel quality report accuracy for eMTC UE |
Qualcomm Incorporated |
R4-2017072 |
Draft CR: Test cases of RLM for MPDCCH performance improvement |
Ericsson |
6.1.4.1 |
UE demodulation requirements [LTE_eMTC5-Perf] |
|
R4-2015836 |
Clean up of enhanced MPDCCH demodulation requirements |
Ericsson |
6.1.4.2 |
CSI requirements [LTE_eMTC5-Perf] |
|
R4-2015837 |
Clean up of CSI-RS based PMI reporting test for non-BL UEs |
Ericsson |
R4-2017458 |
Clean up of CSI-RS based PMI reporting test for non-BL UEs |
Ericsson |
6.2.2 |
RRM core requirements maintenance [NB_IOTenh3-Core] |
|
R4-2015512 |
CR on PUR requirements for NB-IoT |
Huawei, HiSilicon |
R4-2015513 |
CR on RRM requirements for short DRX with eDRX configured for Rel-16 NB-IoT |
Huawei, HiSilicon, Mediatek Inc. |
R4-2017025 |
Email discussion summary for [97e][226] NB_IOTenh3_RRM |
Moderator (Huawei) |
R4-2017074 |
CR on RRM requirements for short DRX with eDRX configured for Rel-16 NB-IoT |
Huawei, HiSilicon, Mediatek Inc. |
R4-2017296 |
Email discussion summary for [97e][226] NB_IOTenh3_RRM |
Moderator (Huawei) |
6.2.3 |
RRM perf. requirements [NB_IOTenh3-Perf] |
|
R4-2017073 |
Big CR: Introduction of Rel-16 Nb-IoT RRM RRM performance requirements (TS 36.133) |
Huawei, HiSilicon |
6.2.3.2 |
Test cases [NB_IOTenh3-Perf] |
|
R4-2015514 |
Draft CR on test cases for UE specific DRX cycles for Rel-16 NB-IoT |
Huawei, HiSilicon |
R4-2015816 |
Test cases of MSG3 channel quality report on non-anchor carrier |
Ericsson |
R4-2015817 |
Draft CR: MSG3 based channel quality reporting on non-anchor carrier |
Ericsson |
R4-2016553 |
Test cases for DLchannel quality report accuracy in RRC_CONNECTED for UE Cat-NB1 Standalone mode |
Qualcomm Incorporated |
R4-2017075 |
Draft CR on test cases for UE specific DRX cycles for Rel-16 NB-IoT |
Huawei, HiSilicon |
R4-2017076 |
Draft CR: MSG3 based channel quality reporting on non-anchor carrier |
Ericsson |
R4-2017077 |
Test cases for DLchannel quality report accuracy in RRC_CONNECTED for UE Cat-NB1 Standalone mode |
Qualcomm Incorporated |
6.2.4.1 |
UE demodulation requirements [NB_IOTenh3-Perf] |
|
R4-2015631 |
CR: Cleanup for NPDSCH performance requirements for multi-TB interleaved transmission in TS 36.101 |
Huawei, HiSilicon |
R4-2017457 |
CR: Cleanup for NPDSCH performance requirements for multi-TB interleaved transmission in TS 36.101 |
Huawei, HiSilicon |
6.2.4.2 |
BS demodulation requirements [NB_IOTenh3-Perf] |
|
R4-2015632 |
CR: Addition of NPUSCH format1 performance requirements for multi-TB interleaved transmission in TS 36.104 |
Huawei, HiSilicon |
R4-2015633 |
CR: Cleanup for NPUSCH format 1 conformance testing for multi-TB interleaved transmission in TS 36.141 |
Huawei, HiSilicon |
6.3 |
Even further Mobility enhancement in E-UTRAN [LTE_feMob] |
|
R4-2017026 |
Email discussion summary for [97e][227] LTE_feMob_RRM |
Moderator (Nokia) |
R4-2017297 |
Email discussion summary for [97e][227] LTE_feMob_RRM |
Moderator (Nokia) |
6.3.1 |
RRM core requirements maintenance [LTE_feMob-Core] |
|
R4-2015502 |
Correction on the synchronous condition for DAPS handover |
Huawei, HiSilicon |
R4-2016385 |
Correction on LTE conditional handover |
Nokia, Nokia Shanghai Bell |
R4-2017079 |
Correction on LTE conditional handover |
Nokia, Nokia Shanghai Bell |
R4-2017322 |
Correction on the synchronous condition for DAPS handover |
Huawei, HiSilicon |
6.3.2 |
RRM perf. requirements [LTE_feMob-Perf] |
|
R4-2017078 |
WF on further test cases for LTE feMob |
Nokia, Nokia Shanghai Bell |
R4-2017374 |
WF on further test cases for LTE feMob |
Nokia, Nokia Shanghai Bell |
6.3.2.2 |
Test cases [LTE_feMob-Perf] |
|
R4-2015501 |
Test cases for inter-frequency DAPS handover |
Huawei, HiSilicon |
R4-2016384 |
Test cases for LTE conditional handover |
Nokia, Nokia Shanghai Bell |
R4-2016554 |
Introduction of intra-frequency sync and async LTE DAPS HO test cases |
Qualcomm Incorporated |
R4-2017308 |
Test cases for LTE conditional handover |
Nokia, Nokia Shanghai Bell |
6.4.2 |
UE RF requirements [WI code] |
|
R4-2014045 |
Correction of B88 UL EARFCN |
Huawei,HiSilicon |
R4-2014162 |
LTE CA_NS_04 PC2 256QAM AMPR |
Qualcomm Inc. |
R4-2014163 |
LTE CA_NS_04 PC2 256QAM AMPR |
Qualcomm Inc. |
R4-2014164 |
CR CatF LTE CA_NS_04 PC2 256QAM AMPR |
Qualcomm |
R4-2014510 |
LTE CA corrections |
Nokia |
R4-2014511 |
Band 88 and 87 bracket removal |
Nokia |
R4-2014897 |
Coexistence cleanup for 36101 Rel16 |
Apple Inc. |
R4-2016008 |
LTE CA_NS_08 A-MPR Correction |
Skyworks Solutions Inc. |
R4-2016040 |
CR Correction to B72 coex - CA_NS_08 - Band 10 protection 36.101 Rel16 |
Skyworks Solutions Inc. |
R4-2016129 |
CR to TS 36.101 clarifications on supported SCS for UE supporting LTE MBMS |
ZTE Corporation |
R4-2016130 |
CR to TS 36.101 clarifications on supported SCS for UE supporting LTE MBMS |
ZTE Corporation |
R4-2016131 |
CR to TS 36.101 clarifications on supported SCS for UE supporting LTE MBMS |
ZTE Corporation |
R4-2016340 |
CR for editorial corrections 36.101 |
Ericsson |
R4-2016426 |
LTE CA_NS_04 PC2 256QAM AMPR |
Qualcomm Incorporated |
R4-2016450 |
CR for 36.101: Corrections for UL CA_41D |
T-Mobile USA |
R4-2016795 |
CR for editorial corrections 36.101 |
Ericsson |
R4-2016997 |
CR Correction to B72 coex - CA_NS_08 - Band 10 protection 36.101 Rel16 |
Skyworks Solutions Inc. |
6.4.3 |
RRM requirements [WI code] |
|
R4-2015879 |
CR on performance requirements tests for euCA. |
Nokia, Nokia Shanghai Bell |
R4-2017062 |
CR on performance requirements tests for euCA. |
Nokia, Nokia Shanghai Bell |
6.4.4.1 |
UE demodulation and CSI requirements [WI code] |
|
R4-2015613 |
CR on cleanup for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
R4-2017459 |
CR on cleanup for LTE-based 5G terrestrial broadcast |
Huawei, HiSilicon |
7.1.1 |
System Parameters [NR_unlic-Core] |
|
R4-2014496 |
[NRU] Justification of band n96 channelization |
Skyworks Solutions Inc. |
R4-2016608 |
Email discussion summary for [97e][106] NR_unlic_SysParameters |
Moderator (Ericsson) |
R4-2016950 |
Email discussion summary for [97e][106] NR_unlic_SysParameters |
Moderator (Ericsson) |
R4-2017835 |
WF on NR-U continuation work |
Skyworks |
7.1.1.1 |
60kHz SCS [NR_unlic-Core] |
|
R4-2014887 |
NR-U 60kHz SCS |
Apple Inc. |
R4-2015694 |
On remaining issues for system parameters |
Huawei, HiSilicon |
7.1.1.2 |
Wideband operation related [NR_unlic-Core] |
|
R4-2014621 |
Discussion on LS on UE capability on wideband carrier operation for NR-U |
MediaTek inc. |
R4-2014888 |
NR-U wideband capabilities |
Apple Inc. |
R4-2015251 |
NR-U - On wideband operation |
Nokia, Nokia Shanghai Bell |
R4-2015972 |
Correction to the intra-cell guard band definition for wideband operation |
Ericsson |
R4-2016438 |
Wideband capability for NR-U |
Qualcomm Incorporated |
R4-2016797 |
Correction to the intra-cell guard band definition for wideband operation |
Ericsson |
R4-2017825 |
Correction to the intra-cell guard band definition for wideband operation |
Ericsson |
R4-2017845 |
Correction to the intra-cell guard band definition for wideband operation |
Ericsson |
7.1.1.3 |
Others [NR_unlic-Core] |
|
R4-2014889 |
NR-U CA bandwidth classes |
Apple Inc. |
R4-2015973 |
Correction to CA bandwidth classes M, N and O |
Ericsson |
R4-2016123 |
Discussion on NR-U channel arrangement for 6GHz |
ZTE Corporation |
R4-2016501 |
NRU small enhancement and exception sheet leftovers beyond RAN4#97e |
Skyworks Solutions Inc. |
7.1.2 |
UE RF requirements [NR_unlic-Core] |
|
R4-2014916 |
CR for TS 38.101-1: NR-U UE RF open requirements |
Apple Inc. |
R4-2015018 |
Architecture and REFSENS discussion for NR-U 6GHz |
MediaTek Inc. |
R4-2015927 |
CR to add NR-U EN-DC combinations |
Ericsson, Charter Communication, T-Mobile US |
R4-2016609 |
Email discussion summary for [97e][107] NR_unlic_UE_RF |
Moderator (Qualcomm) |
R4-2016801 |
CR to add NR-U EN-DC combinations |
Ericsson, Charter Communication, T-Mobile US |
R4-2016951 |
Email discussion summary for [97e][107] NR_unlic_UE_RF |
Moderator (Qualcomm) |
R4-2017391 |
CR to add NR-U EN-DC combinations |
Ericsson, Charter Communication, T-Mobile US |
7.1.2.1 |
Transmitter characteristics [NR_unlic-Core] |
|
R4-2014903 |
PC5 NR-U MPR for NS_53 and NS_54 |
Apple Inc. |
R4-2015697 |
A-MPR evaluation for NR-U |
Huawei, HiSilicon |
R4-2016436 |
Removal of square brackets for 38.101-1 NR-U |
Qualcomm Incorporated |
R4-2016799 |
Removal of square brackets for 38.101-1 NR-U |
Qualcomm Incorporated |
R4-2017837 |
Removal of square brackets for 38.101-1 NR-U |
Qualcomm Incorporated |
7.1.2.2 |
Receiver characteristics [NR_unlic-Core] |
|
R4-2014185 |
Discussion and TP for NR-U UE ACS |
MediaTek Inc. |
R4-2014497 |
[NRU] UE REFSENS for NRU Band n96 |
Skyworks Solutions Inc. |
R4-2015799 |
UE Reference Sensitivity considerations for band n96 |
Charter Communications, Inc |
R4-2015803 |
CR to add NR-DC_n48-n46 combinations |
Charter Communications, Inc |
R4-2015974 |
Correction to receiver requirements for shared spectrum channel access |
Ericsson |
R4-2016294 |
REFSENS for n96 |
Apple Inc. |
R4-2016437 |
Reference sensitivity for NR-U band n96 |
Qualcomm Incorporated |
R4-2016800 |
Correction to receiver requirements for shared spectrum channel access |
Ericsson |
R4-2016802 |
CR to add NR-DC_n48-n46 combinations |
Charter Communications, Inc |
7.1.3 |
Band combination related (Analysis, TPs, etc.) [NR_unlic-Core] |
|
R4-2014954 |
Discussion on NR-U CA bandwidth classes |
ZTE Corporation |
R4-2014955 |
CR to TS 38.101-1 on NR CA bandwidth classes for unlicensed spectrum (Rel-16) |
ZTE Corporation |
R4-2016798 |
CR to TS 38.101-1 on NR CA bandwidth classes for unlicensed spectrum (Rel-16) |
ZTE Corporation |
7.1.4.1 |
General [NR_unlic-Core] |
|
R4-2015371 |
CR to TS 38.104 with NR-U remaining open issues updates |
Nokia, Nokia Shanghai Bell |
R4-2015372 |
On band n96 remaining issues |
Nokia, Nokia Shanghai Bell |
R4-2015698 |
CR for TS 38.104: Corrections for NR-U |
Huawei, HiSilicon |
R4-2016124 |
Discussions on remaining issue of NR-U BS RF requirements |
ZTE Corporation |
R4-2016125 |
CR to 38.104: Corrections on NR-U BS RF requirements |
ZTE Corporation |
R4-2016188 |
CR to 36.104: Introduction of n96 medium range requirements |
Nokia, Nokia Shanghai Bell |
R4-2016189 |
CR to 37.104: Introduction of n96 medium range requirements |
Nokia, Nokia Shanghai Bell |
R4-2016190 |
CR to 37.105: Introduction of n96 medium range requirements |
Nokia, Nokia Shanghai Bell |
R4-2017403 |
Email discussion summary for [97e][305] NR_unlic_RF_BS |
Moderator (Nokia) |
R4-2017461 |
WF on NR-U remaining BS RF core requirements |
Nokia |
R4-2017462 |
CR to TS 38.104 with NR-U remaining open issues updates |
Nokia, Nokia Shanghai Bell |
R4-2017463 |
CR to 36.104: Introduction of n96 medium range requirements |
Nokia, Nokia Shanghai Bell |
R4-2017608 |
Email discussion summary for [97e][305] NR_unlic_RF_BS |
Moderator (Nokia) |
7.1.4.2 |
Transmitter characteristics [NR_unlic-Core] |
|
R4-2015374 |
BS OBUE mask for NR-U |
Nokia, Nokia Shanghai Bell |
R4-2015695 |
On remaining issues for BS TX |
Huawei, HiSilicon |
R4-2015725 |
Discussion on remaining NR-U BS RF Requirements |
Ericsson |
R4-2015726 |
CR to TS 38.104: Removal of |
Ericsson |
7.1.4.3 |
Receiver characteristics [NR_unlic-Core] |
|
R4-2015373 |
On interfering signals for NR-U Rx requirements |
Nokia, Nokia Shanghai Bell |
R4-2015696 |
On remaining issues for BS RX |
Huawei, HiSilicon |
7.1.5.1 |
General [NR_unlic-Perf] |
|
R4-2015384 |
Discussion on NR-U BS RF conformance tests |
Nokia, Nokia Shanghai Bell |
R4-2016126 |
CR to TS 38.141-1: introduction of NR-U into TS 38.141-1 |
ZTE Corporation |
R4-2017404 |
Email discussion summary for [97e][306] NR_unlic_RF_Conformance |
Moderator (ZTE) |
R4-2017464 |
WF on work plan and working split for NR-U BS conformance testing |
ZTE |
R4-2017609 |
Email discussion summary for [97e][306] NR_unlic_RF_Conformance |
Moderator (ZTE) |
7.1.5.2 |
Transmitter characteristics [NR_unlic-Perf] |
|
R4-2015383 |
Draft CR to TS 37.107 With NR-U intorduction for perfromance part |
Nokia, Nokia Shanghai Bell |
7.1.6 |
RRM core requirements maintenance (38.133) [NR_unlic-Core] |
|
R4-2017004 |
Email discussion summary for [97e][205] NR_unlic_RRM_1 |
Moderator (Ericsson) |
R4-2017080 |
WF on NR-U RRM core requirements |
Ericsson |
R4-2017083 |
LS on measuring CSI-RS during SCell activation. |
Ericsson |
R4-2017275 |
Email discussion summary for [97e][205] NR_unlic_RRM_1 |
Moderator (Ericsson) |
R4-2017333 |
LS on SCell activation/deactivation when sCellDeactivationTimer is not configured |
Nokia |
R4-2017381 |
LS on measuring CSI-RS during SCell activation. |
RAN4 |
R4-2017382 |
LS on SCell activation/deactivation when sCellDeactivationTimer is not configured |
Nokia |
7.1.6.1 |
General [NR_unlic-Core] |
|
R4-2014867 |
Discussion on clarification for NR-U RRM requirements with DRX in use |
MediaTek inc. |
R4-2014868 |
Clarification for NR-U RRM requirements with DRX in use |
MediaTek inc. |
R4-2015515 |
Discussion on monitoring capability in cell detection for NR-U |
Huawei, HiSilicon |
R4-2016408 |
On the terminology and SSB monitoring in NR-U |
Ericsson |
R4-2016409 |
Terminology updates for NR-U |
Ericsson |
R4-2016410 |
Terminology updates for NR-U |
Ericsson |
R4-2017081 |
Terminology updates for NR-U |
Ericsson |
R4-2017082 |
Terminology updates for NR-U |
Ericsson |
7.1.6.4 |
RRC connection mobility control [NR_unlic-Core] |
|
R4-2015202 |
CR to 38.133 - Introducing NR-U random access requirements |
Nokia, Nokia Shanghai Bell |
R4-2015386 |
NR-U Random access |
Nokia, Nokia Shanghai Bell |
R4-2016175 |
Analysis of requirements for known cell in RRC re-establishment with CCA |
Ericsson |
R4-2016176 |
Requirements for known cell in RRC re-establishment with CCA |
Ericsson |
7.1.6.5 |
SCell activation/deactivation (delay and interruption) [NR_unlic-Core] |
|
R4-2014013 |
Remaining issues on SCell activation in NR-U |
ZTE Corporation |
R4-2014284 |
On SCell activation requirement for NR-U |
Apple |
R4-2014285 |
Draft CR on SCell activation requirement for NR-U |
Apple |
R4-2015203 |
CR to 38.133 - NR-U SCell activation and deactivation requirements |
Nokia, Nokia Shanghai Bell |
R4-2015385 |
Scell activation and deactivation delay requirements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2015516 |
CR on SCell activation and deactivation requirements for NR-U |
Huawei, HiSilicon |
R4-2015517 |
Discussion on SCell activation and deactivation requirements for NR-U |
Huawei, HiSilicon |
R4-2016411 |
On remaining issues for SCell activation in NR-U |
Ericsson |
R4-2016412 |
Updates in SCell activation in NR-U |
Ericsson |
R4-2016565 |
Remaining Issues On SCell activation and deactivation requirements in NR-U |
Qualcomm Incorporated |
R4-2016591 |
Interruption windows and applicability of Scell activation/deactivation requirements for SCells operating with CCA |
Qualcomm Incorporated |
R4-2017084 |
Interruption windows and applicability of Scell activation/deactivation requirements for SCells operating with CCA |
Qualcomm Incorporated |
7.1.6.6 |
Active TCI state switching [NR_unlic-Core] |
|
R4-2014190 |
On TCI state switching failure in NR-U |
ZTE Corporation |
R4-2015518 |
CR on TCI state switching requirements for NR-U |
Huawei, HiSilicon |
R4-2016585 |
CR to MAC-CE based TCI State Switching requirements for NR-U |
Qualcomm Incorporated |
R4-2017085 |
CR on TCI state switching requirements for NR-U |
Huawei, HiSilicon |
7.1.6.8 |
RLM [NR_unlic-Core] |
|
R4-2015519 |
CR on RLM requirements for NR-U |
Huawei, HiSilicon |
R4-2016413 |
Updates in RLM requirements for NR-U |
Ericsson |
R4-2017086 |
Updates in RLM requirements for NR-U |
Ericsson |
7.1.6.9 |
Beam management [NR_unlic-Core] |
|
R4-2015389 |
Remaining issues in beam management in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2015520 |
CR on Beam mangement requirements for NR-U |
Huawei, HiSilicon |
R4-2015818 |
Open issues on beam management for NR-U |
Ericsson |
R4-2015819 |
CR: Beam management requirements with CCA |
Ericsson |
R4-2017087 |
CR: Beam management requirements with CCA |
Ericsson |
7.1.6.10 |
Measurement requirements [NR_unlic-Core] |
|
R4-2014012 |
Remaining issues in intra and inter-frequency measurements |
ZTE Corporation |
R4-2014869 |
Discussion on measurement requirements for NR-U |
MediaTek inc. |
R4-2014870 |
CR on intra-frequency and inter-frequency measurement with CCA and RSSI measurements |
MediaTek inc. |
R4-2015205 |
CR to 38.133 on NR-U intra-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2015387 |
Remaining aspects in measurement requirements in NR-U |
Nokia, Nokia Shanghai Bell |
R4-2015521 |
CR on intra-frequency measurement requirements for NR-U |
Huawei, HiSilicon |
R4-2015522 |
Discussion on measurement requirements for NR-U |
Huawei, HiSilicon |
R4-2016419 |
Measurementequirements for NR-U |
Ericsson |
R4-2016564 |
Remaining issues on measurement requirements in NR-U |
Qualcomm Incorporated |
R4-2017305 |
Measurement requirements for NR-U |
Ericsson |
7.1.6.11 |
Measurement capability and reporting criteria [NR_unlic-Core] |
|
R4-2014283 |
On measurement capability of NR-U |
Apple |
R4-2015523 |
CR on CSSF RSSI/CO measurement for NR-U |
Huawei, HiSilicon |
R4-2016414 |
Clause numbering correction |
Ericsson |
7.1.6.12 |
Timing [NR_unlic-Core] |
|
R4-2014014 |
Definition of an available reference cell |
ZTE Corporation |
R4-2015204 |
CR to 38.133 - Clarification of NR-U timing requirements |
Nokia, Nokia Shanghai Bell |
R4-2015388 |
On NR-U Timing requirements |
Nokia, Nokia Shanghai Bell |
R4-2015524 |
Discussion on Timing requirements for NR-U |
Huawei, HiSilicon |
R4-2016177 |
Correction to timing requirements in NR-U |
Ericsson |
R4-2016563 |
Definition of Available Reference Cell for Timing Requirements in NR-U |
Qualcomm Incorporated |
R4-2017088 |
Correction to timing requirements in NR-U |
Ericsson |
7.1.6.13 |
Other requirements [NR_unlic-Core] |
|
R4-2015170 |
Updates to general section for NR-U in 38.133 |
Ericsson |
7.1.7 |
RRM perf. requirements (38.133) [NR_unlic-Perf] |
|
R4-2017005 |
Email discussion summary for [97e][206] NR_unlic_RRM_2 |
Moderator (Nokia) |
R4-2017089 |
WF on NR-U RRM Performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2017090 |
LS on clarification of RSSI measurement bandwidth |
Huawei |
R4-2017276 |
Email discussion summary for [97e][206] NR_unlic_RRM_2 |
Moderator (Nokia) |
R4-2017352 |
Draft Big CR: Introduction of Rel-16 NR-U RRM performance requirements |
Ericsson |
7.1.7.1 |
General [NR_unlic-Perf] |
|
R4-2014871 |
Discussion on general test setting for NR-U test cases |
MediaTek inc. |
R4-2015391 |
On NR-U RRM performance |
Nokia, Nokia Shanghai Bell |
R4-2015525 |
CR on RSSI and CO performance requirements for NR-U |
Huawei, HiSilicon |
R4-2015526 |
Discussion on performance requirements for RSSI measurement for NR-U |
Huawei, HiSilicon |
R4-2016415 |
General discussion on NR-U RRM test cases |
Ericsson |
R4-2016418 |
Measurement accuracy requirements for NR-U |
Ericsson |
R4-2016566 |
RSSI Measurement Accuracy Requirements in NR-U |
Qualcomm Incorporated |
R4-2017091 |
Measurement accuracy requirements for NR-U |
Ericsson |
7.1.7.2 |
Test cases [NR_unlic-Perf] |
|
R4-2014872 |
Discussion on RRM test cases in NR-U |
MediaTek inc. |
R4-2015390 |
On NR-U RRM test cases |
Nokia, Nokia Shanghai Bell |
R4-2016416 |
NR-U RRM test case list and time plan |
Ericsson |
R4-2016417 |
NR-U test cases structure |
Ericsson |
R4-2016567 |
NR-U RRM Performance Work Plan and Work Split |
Qualcomm Incorporated |
R4-2017092 |
NR-U test cases structure |
Ericsson |
R4-2017332 |
NR-U RRM Performance Work Plan |
Qualcomm Incorporated |
7.1.8.1 |
General [NR_unlic-Perf] |
|
R4-2014240 |
Discussion on demodulation requirements for NR-U |
Apple |
R4-2014940 |
General Demodulation performance requirements for NR-U |
Nokia, Nokia Shanghai Bell |
R4-2015130 |
Discussion on UE performance requirement for NR-U |
MediaTek inc. |
R4-2015851 |
discussion on general issues in NR-U performance requirements |
Ericsson |
R4-2015986 |
Discussion on NR-U General aspects |
Intel Corporation |
R4-2016063 |
DL Transmission Model Definition for NR-U Demod Performances |
Qualcomm Incorporated |
R4-2017413 |
Email discussion summary for [97e][315] NR_unlic_Demod_UE |
Moderator (Qualcomm) |
R4-2017414 |
Email discussion summary for [97e][316] NR_unlic_Demod_BS |
Moderator (Huawei) |
R4-2017465 |
Way Forward on NR-U UE demodulation requirements |
Qualcomm |
R4-2017466 |
Way forward on NR-U BS demodulation requirements for general part and PUSCH |
Huawei, HiSilicon |
R4-2017467 |
Way forward on PUCCH demodulation requirements |
Ericsson |
R4-2017468 |
Way forward on PRACH demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017610 |
Email discussion summary for [97e][315] NR_unlic_Demod_UE |
Moderator (Qualcomm) |
R4-2017611 |
Email discussion summary for [97e][316] NR_unlic_Demod_BS |
Moderator (Huawei) |
R4-2017685 |
Way Forward on NR-U UE demodulation requirements |
Qualcomm |
R4-2017688 |
Way forward on NR-U BS demodulation requirements for general part and PUSCH |
Huawei, HiSilicon |
7.1.8.2.1 |
PDSCH requirements [NR_unlic-Perf] |
|
R4-2015634 |
Discussion on NR-U PDSCH performance requirements |
Huawei, HiSilicon |
R4-2015987 |
Discussion on NR-U PDSCH requirements |
Intel Corporation |
R4-2016064 |
Simulation Assumptions for NR-U PDSCH Demodulation Performance Tests |
Qualcomm Incorporated |
R4-2016089 |
Discussion on NR-U PDSCH demodulation requirements |
Ericsson |
7.1.8.2.2 |
PDCCH requirements [NR_unlic-Perf] |
|
R4-2015635 |
Discussion on NR-U PDCCH performance requirements |
Huawei, HiSilicon |
R4-2016090 |
Discussion on NR-U PDCCH demodulation requirements |
Ericsson |
7.1.8.3 |
CSI requirements [NR_unlic-Perf] |
|
R4-2015636 |
Discussion on NR-U CSI requirements |
Huawei, HiSilicon |
R4-2016091 |
Discussion on NR-U CSI performance requirements |
Ericsson |
7.1.8.4 |
BS demodulation requirements [NR_unlic-Perf] |
|
R4-2015117 |
View on BS demodulation requirement for NR-U |
Samsung |
7.1.8.4.1 |
PUSCH requirements [NR_unlic-Perf] |
|
R4-2014941 |
PUSCH Demodulation performance requirements for operation in unlicensed bands |
Nokia, Nokia Shanghai Bell |
R4-2015637 |
Discussion on NR-U PUSCH performance requirements |
Huawei, HiSilicon |
R4-2015852 |
discussion on NR-U PUSCH demodulation assumptions |
Ericsson |
R4-2015988 |
Discussion on NR-U PUSCH requirements |
Intel Corporation |
7.1.8.4.2 |
PUCCH requirements [NR_unlic-Perf] |
|
R4-2014942 |
PUCCH Demodulation performance requirements for operation in unlicensed bands |
Nokia, Nokia Shanghai Bell |
R4-2015638 |
Discussion on NR-U PUCCH performance requirements |
Huawei, HiSilicon |
R4-2015853 |
discussion on NR-U PUCCH demodulation assumptions |
Ericsson |
R4-2015989 |
Discussion on NR-U PUCCH requirements |
Intel Corporation |
7.1.8.4.3 |
PRACH requirements [NR_unlic-Perf] |
|
R4-2014943 |
PRACH Demodulation performance requirements for operation in unlicensed bands |
Nokia, Nokia Shanghai Bell |
R4-2015639 |
Discussion on NR-U PRACH performance requirements |
Huawei, HiSilicon |
R4-2015854 |
discussion on NR-U PRACH demodulation assumptions |
Ericsson |
R4-2015990 |
Discussion on NR-U PRACH requirements |
Intel Corporation |
7.2 |
NR mobility enhancement [NR_Mob_enh] |
|
R4-2017006 |
Email discussion summary for [97e][207] NR_Mob_enh_RRM |
Moderator (Apple) |
R4-2017093 |
WF on NR mobility enhancement |
Apple |
R4-2017277 |
Email discussion summary for [97e][207] NR_Mob_enh_RRM |
Moderator (Apple) |
7.2.1 |
RRM core requirements maintenance (38.133) [NR_Mob_enh-Core] |
|
R4-2014357 |
Discussion on dual active protocol stack handover |
MediaTek inc. |
R4-2014358 |
CR on TS38.133 for dual active protocol stack handover |
MediaTek inc. |
R4-2015167 |
AGC operation in async intra-frequency DAPS HO |
Ericsson |
R4-2015168 |
Corrections to DAPS requirements |
Ericsson |
R4-2015464 |
CR on maintaining DAPS handover requirements |
Huawei, HiSilicon |
R4-2016016 |
CR 38.133 Corrections to Conditional PSCell Change delay requirement |
Ericsson |
R4-2017094 |
CR on TS38.133 for dual active protocol stack handover |
MediaTek inc. |
R4-2017095 |
Corrections to DAPS requirements |
Ericsson |
7.2.2.1 |
General [NR_Mob_enh-Perf] |
|
R4-2014222 |
Discussion on DAPS HO test applicability |
Apple |
R4-2014223 |
CR for DAPS HO test applicability |
Apple |
7.2.2.2 |
Test cases [NR_Mob_enh-Perf] |
|
R4-2014580 |
Intra-band Inter-frequency sync DAPS handover test in SA for FR1 |
Intel Corporation |
R4-2015169 |
Conditional handover test cases for NR |
Ericsson |
R4-2015465 |
Discussion on DAPS handover test cases |
Huawei, HiSilicon |
R4-2015466 |
DraftCR on inter-band DAPS handover tests |
Huawei, HiSilicon |
R4-2016555 |
Introduction of intra-frequency sync and async DAPS HO test cases in FR1 |
Qualcomm Incorporated |
R4-2017096 |
Intra-band Inter-frequency sync DAPS handover test in SA for FR1 |
Intel Corporation |
R4-2017097 |
Conditional handover test cases for NR |
Ericsson |
R4-2017098 |
CR on inter-band DAPS handover tests |
Huawei, HiSilicon |
R4-2017099 |
Introduction of intra-frequency sync and async DAPS HO test cases in FR1 |
Qualcomm Incorporated |
R4-2017351 |
Intra-band Inter-frequency sync DAPS handover test in SA for FR1 |
Intel Corporation |
7.3.1 |
General [5G_V2X_NRSL] |
|
R4-2014972 |
CR on TS38.101-1 for NR V2X |
vivo |
R4-2016474 |
draft CR for 38.101-1 NR V2X FRC |
Huawei, HiSilicon |
R4-2016610 |
Email discussion summary for [97e][108] 5G_V2X_NRSL_UE_RF |
Moderator (LG Electronics) |
R4-2016952 |
Email discussion summary for [97e][108] 5G_V2X_NRSL_UE_RF |
Moderator (LG Electronics) |
R4-2017811 |
LS on Rel-16 RAN4 Clarification for UE Antenna Connector Interpretation |
RAN4 |
R4-2017822 |
CR for 38.101-1 NR V2X FRC |
Huawei, HiSilicon |
7.3.3 |
UE RF requirements maintenance [5G_V2X_NRSL-Core] |
|
R4-2014323 |
Correction on 5G V2X UE RF requirements in TS38.101-1 in rel-16 |
LG Electronics France |
R4-2014325 |
Correction on update 5G V2X UE RF requirements in TR38.886 |
LG Electronics France |
R4-2016803 |
Correction on 5G V2X UE RF requirements in TS38.101-1 in rel-16 |
LG Electronics France |
R4-2016804 |
Correction on update 5G V2X UE RF requirements in TR38.886 |
LG Electronics France |
7.3.3.1 |
Transmitter characteristics [5G_V2X_NRSL-Core] |
|
R4-2014321 |
UE-to-UE coexistence and other remaining issues for V2X operation |
LG Electronics France |
R4-2015333 |
CR on V2X bands reference table |
OPPO |
R4-2016447 |
Revision of inter-band V2X con-currency table for V2X_n71A_n47A |
Qualcomm Incorporated |
R4-2016805 |
CR on V2X bands reference table |
OPPO |
7.3.3.2 |
Receiver characteristics [5G_V2X_NRSL-Core] |
|
R4-2016446 |
Revised V2X FRC tables |
Qualcomm Incorporated |
7.3.4 |
Concurrent operation maintenance (scenarios, requirements, etc) [5G_V2X_NRSL-Core] |
|
R4-2014324 |
Correction on 5G V2X inter-band con-current UE RF requirements in TS38.101-3 |
LG Electronics France |
R4-2016611 |
Email discussion summary for [97e][109] 5G_V2X_NRSL_UE_Concurrent |
Moderator (Huawei) |
R4-2016806 |
WF on SL switching period |
Huawei, HiSilicon |
R4-2016807 |
LS on SL switching priority |
Xiaomi |
R4-2016810 |
Correction on 5G V2X inter-band con-current UE RF requirements in TS38.101-3 |
LG Electronics France |
R4-2016953 |
Email discussion summary for [97e][109] 5G_V2X_NRSL_UE_Concurrent |
Moderator (Huawei) |
R4-2017839 |
LS on SL switching priority |
RAN4 |
7.3.4.1 |
Transmitter characteristics [5G_V2X_NRSL-Core] |
|
R4-2014414 |
Discussion on switching period for NR V2X in ITS band |
CATT |
R4-2014416 |
CR for 38.886, Time mask for TDM between NR V2X and LTE V2X in ITS band |
CATT |
R4-2014596 |
General corrections for V2X sections in 38.101-3 |
Qualcomm Incorporated |
R4-2014641 |
NR V2X inter-RAT Tx switch |
Qualcomm, Inc. |
R4-2014971 |
Further discussion on switching period for NR V2X |
vivo |
R4-2015253 |
CR for TS 38.101-3 switching period for V2X con-current operation |
Xiaomi |
R4-2015257 |
on switching period |
Xiaomi |
R4-2015267 |
CR for TS 38.101-3 switching period for V2X con-current operation |
Beijing Xiaomi Electronics |
R4-2016475 |
On NR V2X switching period |
Huawei, HiSilicon |
R4-2016476 |
draft correction CR for TS 38.101-3: NR V2X con-current operation |
Huawei, HiSilicon |
R4-2016809 |
CR for 38.886, Time mask for TDM between NR V2X and LTE V2X in ITS band |
CATT |
R4-2016811 |
General corrections for V2X sections in 38.101-3 |
Qualcomm Incorporated |
7.3.4.2 |
Receiver characteristics [5G_V2X_NRSL-Core] |
|
R4-2014322 |
MSD Analysis results and harmonic reduction filter for V2X_20A_n38A |
LG Electronics France |
R4-2014415 |
CR for TS 38.101-3, Time mask for TDM operation between NR V2X and LTE V2X in ITS band |
CATT |
R4-2016808 |
CR for TS 38.101-3, Time mask for TDM operation between NR V2X and LTE V2X in ITS band |
CATT |
7.3.5 |
RRM core requirements maintenance (38.133) [5G_V2X_NRSL-Core] |
|
R4-2014213 |
On interruption requirement on LTE SL due to changing of NR SL sync source |
ZTE Corporation |
R4-2014294 |
Discussion of maintenace issues for NR V2X |
LG Electronics Inc. |
R4-2014295 |
CR of NR V2X operating band group |
LG Electronics Inc. |
R4-2014634 |
NR V2X RRM core and performance requirement remaining issues |
Qualcomm, Inc. |
R4-2014635 |
CR: Interruption requirement for NR V2X synchronization source chang |
Qualcomm, Inc. |
R4-2014767 |
Remaining issues on NR V2X RRM requirement |
MediaTek inc. |
R4-2017007 |
Email discussion summary for [97e][208] 5G_V2X_NRSL_RRM |
Moderator (LG Electronics) |
R4-2017100 |
WF on NR V2X RRM requirements |
LG Electronics |
R4-2017101 |
CR of NR V2X operating band group |
LG Electronics Inc. |
R4-2017278 |
Email discussion summary for [97e][208] 5G_V2X_NRSL_RRM |
Moderator (LG Electronics) |
R4-2017345 |
CR: Interruption requirement for NR V2X synchronization source chang |
Qualcomm, Inc. |
7.3.6 |
RRM perf. requirements (38.133) [5G_V2X_NRSL-Perf] |
|
R4-2017105 |
Draft Big CR: Introduction of Rel-16 NR V2X RRM performance requirements (TS 38.133) |
LG Electronics |
7.3.6.1 |
General [5G_V2X_NRSL-Perf] |
|
R4-2014296 |
CR of NR V2X measurement accuracy requirements(SL-RSSI and L1 SL-RSRP) |
LG Electronics Inc. |
R4-2014298 |
CR of Annex.B for NR V2X side conditions |
LG Electronics Inc. |
R4-2014768 |
Discussion on L1 SL-RSRP measurement test case |
MediaTek inc. |
R4-2017102 |
CR of NR V2X measurement accuracy requirements(SL-RSSI and L1 SL-RSRP) |
LG Electronics Inc. |
R4-2017103 |
CR of Annex.B for NR V2X side conditions |
LG Electronics Inc. |
7.3.6.2 |
L1 SL-RSRP measurement accuracy [5G_V2X_NRSL-Perf] |
|
R4-2015467 |
DraftCR on PSBCH-RSRP accuracy requirements |
Huawei, HiSilicon |
R4-2017104 |
DraftCR on PSBCH-RSRP accuracy requirements |
Huawei, HiSilicon |
7.3.6.3 |
Test cases [5G_V2X_NRSL-Perf] |
|
R4-2014640 |
NR V2X RRM test case discussion |
Qualcomm, Inc. |
7.3.6.3.1 |
UE transmit timing [5G_V2X_NRSL-Perf] |
|
R4-2015469 |
DraftCR on UE Transmission Timing Accuracy Tests for NR V2X |
Huawei, HiSilicon |
R4-2017106 |
DraftCR on UE Transmission Timing Accuracy Tests for NR V2X |
Huawei, HiSilicon |
7.3.6.3.2 |
Initiation/Cease of SLSS Transmission [5G_V2X_NRSL-Perf] |
|
R4-2014299 |
draft CR of Test for initiation and cease of SLSS Transmission with V2X Sidelink Communication |
LG Electronics Inc. |
R4-2014655 |
RRM test cases for NR V2X Synchronization Reference Selection/Reselection |
Xiaomi |
R4-2017107 |
draft CR of Test for initiation and cease of SLSS Transmission with V2X Sidelink Communication |
LG Electronics Inc. |
R4-2017108 |
RRM test cases for NR V2X Synchronization Reference Selection/Reselection |
Xiaomi |
7.3.6.3.3 |
Selection / Reselection of V2X Synchronization Reference Source [5G_V2X_NRSL-Perf] |
|
R4-2014214 |
Selection or Reselection of V2X Synchronization Reference Source |
ZTE Corporation |
7.3.6.3.4 |
L1 SL-RSRP measurements [5G_V2X_NRSL-Perf] |
|
R4-2014212 |
On L1 SL-RSRP accuracy for NR V2X |
ZTE Corporation |
R4-2014639 |
CR: RRM autonomous resource selection test cases for NR V2X |
Qualcomm, Inc. |
R4-2014769 |
CR on V2X UE Resource Selection Tests for Re-evaluation |
MediaTek inc. |
R4-2015468 |
Discussion on UE Autonomous Resource Selection/Reselection Test for NR V2X |
Huawei, HiSilicon |
R4-2017109 |
CR: RRM autonomous resource selection test cases for NR V2X |
Qualcomm, Inc. |
R4-2017110 |
CR on V2X UE Resource Selection Tests for Re-evaluation |
MediaTek inc. |
7.3.6.3.5 |
Congestion control measurements [5G_V2X_NRSL-Perf] |
|
R4-2014770 |
CR on V2X UE Congestion Control Measurement Test |
MediaTek inc. |
R4-2017111 |
CR on V2X UE Congestion Control Measurement Test |
MediaTek inc. |
R4-2017347 |
CR on V2X UE Congestion Control Measurement Test |
MediaTek inc. |
7.3.6.3.6 |
Interruptions [5G_V2X_NRSL-Perf] |
|
R4-2015470 |
DraftCR on Interruption Tests for NR V2X |
Huawei, HiSilicon |
R4-2017112 |
DraftCR on Interruption Tests for NR V2X |
Huawei, HiSilicon |
7.3.7.1 |
General [5G_V2X_NRSL-Perf] |
|
R4-2014419 |
Simulation results of NR V2X demodulation test |
CATT |
R4-2014537 |
Discussion on V2X work scope and general simulation assumptions |
Intel Corporation |
R4-2014779 |
Discussion on V2X Demod test case |
MediaTek inc. |
R4-2017415 |
Email discussion summary for [97e][317] V2X_Demod_Part1 |
Moderator (LGE) |
R4-2017416 |
Email discussion summary for [97e][318] V2X_Demod_Part2 |
Moderator (Intel) |
R4-2017469 |
WF on single link tests for NR V2X demodulation performance |
LGE |
R4-2017470 |
Simulation assumptions for NR V2X single link test case |
Huawei |
R4-2017471 |
WF on multiple link tests for NR V2X demodulation performance |
Intel |
R4-2017472 |
Simulation assumptions for NR V2X multiple link test case |
Huawei |
R4-2017612 |
Email discussion summary for [97e][317] V2X_Demod_Part1 |
Moderator (LGE) |
R4-2017613 |
Email discussion summary for [97e][318] V2X_Demod_Part2 |
Moderator (Intel) |
R4-2017686 |
WF on multiple link tests for NR V2X demodulation performance |
Intel |
R4-2017687 |
WF on single link tests for NR V2X demodulation performance |
LGE |
7.3.7.2 |
Single link test [5G_V2X_NRSL-Perf] |
|
R4-2014417 |
Discussion on single link demodulation test for NR V2X |
CATT |
R4-2014420 |
CR for 38.101-1: Introduce PSBCH performance requirements for NR V2X |
CATT |
R4-2014538 |
Discussion on Single Link V2X requirements |
Intel Corporation |
R4-2014637 |
NR V2X Demod single link requirement |
Qualcomm, Inc. |
R4-2014652 |
Discussion on NR V2X single link test cases |
LG Electronics Inc. |
R4-2014668 |
Initial simulation results for NR V2X single link test cases |
LG Electronics Inc. |
R4-2014780 |
CR on NR V2X PSFCH demodulation requirements |
MediaTek inc. |
R4-2015640 |
Discussion on performance requirements for NR V2X single-link test |
Huawei, HiSilicon |
R4-2015641 |
Simulation results for NR V2X single-link test |
Huawei, HiSilicon |
7.3.7.3 |
Multiple link test [5G_V2X_NRSL-Perf] |
|
R4-2014418 |
Discussion on multiple link demodulation test for NR V2X |
CATT |
R4-2014539 |
Discussion on Multiple Link V2X requirements |
Intel Corporation |
R4-2014636 |
NR V2X Demod multiple linkrequirement |
Qualcomm, Inc. |
R4-2014638 |
CR: Demod HARQ buffer soft combining test cases for NR V2X |
Qualcomm, Inc. |
R4-2014669 |
Discussion on NR V2X multiple link test cases |
LG Electronics Inc. |
R4-2014670 |
Initial simulation results for NR V2X multiple link test cases |
LG Electronics Inc. |
R4-2015642 |
Discussion on performance requirements for NR V2X multi-link test |
Huawei, HiSilicon |
R4-2015643 |
Draft CR: Introduce power imbalance with two links test for NR sidelink |
Huawei, HiSilicon |
R4-2015644 |
Draft CR: Introduce PSCCH/PSSCH decoding capability test for NR sidelink |
Huawei, HiSilicon |
R4-2015645 |
Draft CR: PSFCH decoding capability test for NR sidelink |
Huawei, HiSilicon |
7.4.1 |
General [NR_IAB-Core] |
|
R4-2016139 |
Draft CR to TS 38.174: IAB General and RF core maintenance |
ZTE Corporation |
R4-2017405 |
Email discussion summary for [97e][307] NR_IAB_General |
Moderator (CATT) |
R4-2017474 |
Draft CR to TS 38.174: maintenance of TS 38.174 References and Definitions |
Nokia |
R4-2017475 |
Draft CR to TS 38.174: maintenance of TS 38.174 Symbols and Abbreviations |
Huawei |
R4-2017614 |
Email discussion summary for [97e][307] NR_IAB_General |
Moderator (CATT) |
R4-2017642 |
Draft CR to TS 38.174: maintenance of TS 38.174 clause 4 |
Ericsson |
R4-2017643 |
Draft CR to TS 38.174: add new sub-clauses to TS 38.174 clause 4 |
ZTE |
R4-2017644 |
Draft CR to TS 38.174: maintenance of TS 38.174 clause 5 |
CATT |
7.4.1.1 |
System parameters maintenance [NR_IAB-Core] |
|
R4-2014384 |
Draft CR to TS 38.174: IAB-MT CA support and maintanance of clause 4 to 5 |
CATT |
R4-2014752 |
Correction CR on TR38.809 |
Samsung |
R4-2015433 |
DraftCR to TS 38.174: System parameter corrections |
Nokia, Nokia Shanghai Bell |
R4-2016081 |
draftCR to TS 38.147: IAB-MT number of TRX |
Huawei |
R4-2016251 |
CR on System parameters maintenance |
Ericsson |
R4-2016260 |
CR on System parameters |
Ericsson |
R4-2017473 |
Correction CR on TR38.809 |
Samsung |
R4-2017664 |
Correction CR on TS38.174 |
Qualcomm |
7.4.1.2 |
Others [NR_IAB-Core] |
|
R4-2014385 |
Draft CR to TS 38.174: maintanance of references and definitions |
CATT |
R4-2014751 |
Draft CR with correction on section 4 |
Samsung |
R4-2015434 |
DraftCR to TS 38.174: General section corrections |
Nokia, Nokia Shanghai Bell |
R4-2016083 |
draftCR to TS 38.174: Definitions, symbols and abreviations |
Huawei |
R4-2016250 |
CR on general requirements in TS 38.174 |
Ericsson |
R4-2016259 |
CR on general requirements in TR 38.809 |
Ericsson |
7.4.2 |
RF requirements maintenance [NR_IAB-Core] |
|
R4-2017406 |
Email discussion summary for [97e][308] NR_IAB_RF_Maintenance |
Moderator (Qualcomm) |
R4-2017615 |
Email discussion summary for [97e][308] NR_IAB_RF_Maintenance |
Moderator (Qualcomm) |
7.4.2.1 |
Transmitter characteristics [NR_IAB-Core] |
|
R4-2016137 |
Further discussion on IAB-MT power control and EVM measurement |
ZTE Corporation |
7.4.2.1.1 |
Tx Power related requirements [NR_IAB-Core] |
|
R4-2016257 |
CR on Tx Power related requirements |
Ericsson |
R4-2016264 |
CR on Tx Power related requirements chapter |
Ericsson |
R4-2017482 |
CR on Tx Power related requirements |
Ericsson |
7.4.2.1.2 |
Transmitted signal quality [NR_IAB-Core] |
|
R4-2014386 |
Draft CR to TS 38.174: Transmitted signal quality maintainance |
CATT |
R4-2014387 |
Draft CR to TS 38.809: Transmitted signal quality maintainance |
CATT |
R4-2015207 |
IAB EVM procedure and other consideration |
Nokia, Nokia Shanghai Bell |
R4-2015435 |
DraftCR to TS 38.174: Transmitted signal quality |
Nokia, Nokia Shanghai Bell |
R4-2016082 |
draft CR to TS 38.174 - Correction of IAB-modulation quality sub-clause. |
Huawei |
R4-2016255 |
CR on Tx signal quality requirements |
Ericsson |
R4-2016263 |
CR on Tx signal quality related requirements chapter |
Ericsson |
R4-2017476 |
Draft CR to TS 38.174: Transmitted signal quality maintainance |
CATT |
R4-2017477 |
Draft CR to TS 38.809: Transmitted signal quality maintainance |
CATT |
R4-2017478 |
CR on Tx signal quality related requirements chapter |
Ericsson |
7.4.2.1.3 |
Unwanted emissions [NR_IAB-Core] |
|
R4-2016258 |
CR on unwanted emission requirements |
Ericsson |
R4-2016265 |
CR on unwanted emission requirements chapter |
Ericsson |
R4-2017483 |
CR on unwanted emission requirements |
ZTE |
7.4.2.1.4 |
Others [NR_IAB-Core] |
|
R4-2014388 |
Discussion on IAB-MT EVM measurement process |
CATT |
R4-2016256 |
CR on Tx characteristic other requirements |
Ericsson |
R4-2017486 |
CR on Tx characteristic other requirements |
Ericsson |
7.4.2.2.1 |
Sensitivity and dynamic range requirements [NR_IAB-Core] |
|
R4-2015436 |
DraftCR to TS 38.174: Sensitivity corrections |
Nokia, Nokia Shanghai Bell |
R4-2016254 |
CR on Sensitivity and dynamic range related requirements |
Ericsson |
R4-2016262 |
CR on Sensitivity and dynamic range related requirements chapter |
Ericsson |
R4-2017479 |
DraftCR to TS 38.174: Sensitivity corrections |
Nokia, Nokia Shanghai Bell |
R4-2017651 |
draftCR to TS 38.174: Section 10.2 OTA sensitivity |
Huawei |
7.4.2.2.2 |
In-band selectivity and blocking requirements [NR_IAB-Core] |
|
R4-2015437 |
DraftCR to TS 38.174: In-band selectivity corrections |
Nokia, Nokia Shanghai Bell |
R4-2016252 |
CR on Inband selectivity and blocking requirements |
Ericsson |
R4-2016261 |
CR on Inband selectivity and blocking requirements chapter |
Ericsson |
R4-2017480 |
DraftCR to TS 38.174: In-band selectivity corrections |
Nokia, Nokia Shanghai Bell |
R4-2017481 |
CR on Inband selectivity and blocking requirements |
Ericsson |
7.4.2.2.3 |
Others [NR_IAB-Core] |
|
R4-2015438 |
DraftCR to TS 38.174: OOB blocking and Rx spurious corrections |
Nokia, Nokia Shanghai Bell |
R4-2016253 |
CR on Rx Charateristic other related requirements |
Ericsson |
R4-2017484 |
DraftCR to TS 38.174: OOB blocking and Rx spurious corrections |
Nokia, Nokia Shanghai Bell |
R4-2017485 |
CR on Rx Charateristic other related requirements |
Ericsson |
7.4.3.1 |
General and work plan [NR_IAB-Perf] |
|
R4-2014484 |
IAB RF Conformance Testing |
Qualcomm Incorporated |
R4-2014750 |
On IAB conformance testing |
Samsung |
R4-2015439 |
IAB RF conformance testing framework |
Nokia, Nokia Shanghai Bell |
R4-2016084 |
Discussion on conformance specification |
Huawei |
R4-2016245 |
On IAB conformance testing |
Ericsson |
R4-2017407 |
Email discussion summary for [97e][309] NR_IAB_Conformance_Part1 |
Moderator (Nokia) |
R4-2017408 |
Email discussion summary for [97e][310] NR_IAB_Conformance_Part2 |
Moderator (Samsung) |
R4-2017487 |
WF on IAB conformance work plan and specifications |
Qualcomm |
R4-2017488 |
WF and test setup and test environments |
Nokia, Nokia Shanghai Bell |
R4-2017489 |
WF on manufacturer declarations, test models and configurations including Rx FRC |
Ericsson |
R4-2017490 |
WF on dynamic range, power control (LA) and frequency error for IAB-MT |
CATT |
R4-2017491 |
WF on detail aspects on IAB conformance testing |
Nokia |
R4-2017616 |
Email discussion summary for [97e][309] NR_IAB_Conformance_Part1 |
Moderator (Nokia) |
R4-2017617 |
Email discussion summary for [97e][310] NR_IAB_Conformance_Part2 |
Moderator (Samsung) |
R4-2017671 |
WF and test setup and test environments |
Nokia, Nokia Shanghai Bell |
R4-2017672 |
WF on manufacturer declarations, test models and configurations including Rx FRC |
Ericsson |
7.4.3.2 |
Common test issues for conducted and radiated conformance testing [NR_IAB-Perf] |
|
R4-2016138 |
Discussion on IAB conformance testing |
ZTE Corporation |
7.4.3.2.1 |
Test configurations [NR_IAB-Perf] |
|
R4-2014389 |
Discussion on IAB RF test configuration |
CATT |
R4-2014485 |
IAB RF Testing |
Qualcomm Incorporated |
R4-2015440 |
Test configurations for IAB RF conformance testing |
Nokia, Nokia Shanghai Bell |
R4-2016243 |
IAB Common test issue on test configuration |
Ericsson |
7.4.3.2.2 |
Test models [NR_IAB-Perf] |
|
R4-2014390 |
Discussion on IAB RF test model |
CATT |
R4-2016244 |
IAB Common test issue on test model |
Ericsson |
7.4.3.2.3 |
Others [NR_IAB-Perf] |
|
R4-2016242 |
IAB Common test issue on enviroment conditions |
Ericsson |
7.4.3.3.1 |
Transmitter characteristics [NR_IAB-Perf] |
|
R4-2014391 |
Discussion on the reference conditions of IAB-MT output power dynamics |
CATT |
R4-2015441 |
Radiated conformance testing, Tx requirements |
Nokia, Nokia Shanghai Bell |
R4-2016246 |
Conducted transmitter characteristic test |
Ericsson |
7.4.3.3.2 |
Receiver characteristics [NR_IAB-Perf] |
|
R4-2015442 |
Radiated conformance testing, Rx requirements |
Nokia, Nokia Shanghai Bell |
R4-2016247 |
Conducted receiver characteristic test |
Ericsson |
7.4.3.4.1 |
Transmitter characteristics [NR_IAB-Perf] |
|
R4-2016248 |
Radiated transmitter characteristic test |
Ericsson |
7.4.3.4.2 |
Receiver characteristics [NR_IAB-Perf] |
|
R4-2016249 |
Radiated receiver characteristic test |
Ericsson |
7.4.4 |
RRM core requirements maintenance [NR_IAB-Core] |
|
R4-2015508 |
CR on Link recovery for IAB-MT |
Huawei, HiSilicon |
R4-2015509 |
CR on RLM for IAB-MT |
Huawei, HiSilicon |
R4-2015790 |
CR on Link recovery for IAB-MT |
Huawei, HiSilicon |
R4-2015791 |
CR on RLM for IAB-MT |
Huawei, HiSilicon |
R4-2016028 |
DraftCR for TR38.809: IAB RRM general |
Samsung |
R4-2016170 |
Symbols, abbreviations and definitions for IAB RRM in 38.174 |
Ericsson |
R4-2016171 |
Issues with IAB RRM requirements |
Ericsson |
R4-2016382 |
Correction on IAB RRM requirements in TS 38.174 |
Nokia, Nokia Shanghai Bell |
R4-2017008 |
Email discussion summary for [97e][209] NR_IAB_RRM |
Moderator (ZTE Corporation) |
R4-2017113 |
Symbols, abbreviations and definitions for IAB RRM in 38.174 |
Ericsson |
R4-2017114 |
Correction on IAB RRM requirements in TS 38.174 |
Nokia, Nokia Shanghai Bell |
R4-2017279 |
Email discussion summary for [97e][209] NR_IAB_RRM |
Moderator (ZTE Corporation) |
7.4.5 |
RRM perf. requirements [NR_IAB-Perf] |
|
R4-2017115 |
WF on test cases for IAB-MTs |
ZTE Corporation |
R4-2017383 |
WF on test cases for IAB-MTs |
ZTE Corporation |
7.4.5.1 |
General [NR_IAB-Perf] |
|
R4-2014009 |
Scope of test cases for IAB-MTs |
ZTE Corporation |
R4-2015510 |
Discussion on performance requirements for IAB |
Huawei, HiSilicon |
R4-2016172 |
Specification structure for IAB-MT RRM test cases in 38.174 |
Ericsson |
R4-2016173 |
Principles for IAB RRM test cases |
Ericsson |
R4-2016174 |
IAB RRM test case list |
Ericsson |
R4-2016383 |
discussion on IAB RRM test cases |
Nokia, Nokia Shanghai Bell |
R4-2016594 |
Scope of test cases for IAB-MTs |
ZTE Corporation, Qualcomm Incorporated |
R4-2017117 |
Specification structure for IAB-MT RRM test cases in 38.174 |
Ericsson |
7.4.5.2 |
Test cases [NR_IAB-Perf] |
|
R4-2014184 |
[draft CR] Test cases for timing for IAB-MT |
ZTE Corporation |
R4-2015511 |
Discussion on test cases for IAB |
Huawei, HiSilicon |
R4-2017116 |
[draft CR] Test cases for timing for IAB-MT |
ZTE Corporation |
7.4.6.1 |
General [NR_IAB-Core] |
|
R4-2015026 |
CR to TS 38.175: IAB definition |
ZTE Corporation |
R4-2015106 |
CR to TS 38.175 on Voltage dips and interruptions, Release 16 |
Ericsson |
R4-2015107 |
Definition of Exclusion Bands for IAB EMC nodes |
Ericsson |
R4-2015108 |
CR to TS 38.175 on Exclusion Bands |
Ericsson |
R4-2017444 |
CR to TS 38.175 on Voltage dips and interruptions, Release 16 |
Ericsson |
7.4.6.2 |
Emission requirements [NR_IAB-Core] |
|
R4-2015027 |
CR to TS 38.175: Radiated emission, IAB |
ZTE Corporation |
R4-2015109 |
Discussion on IAB EMC Radiated Emissions |
Ericsson |
R4-2015110 |
CR to TS 38.175 on IAB EMC Emission |
Ericsson |
R4-2017442 |
CR to TS 38.175: Radiated emission, IAB |
ZTE Corporation, Ericsson |
7.4.6.3 |
Immunity requirements [NR_IAB-Core] |
|
R4-2015111 |
Discussion on Spatial Exclusion for IAB EMC RI test |
Ericsson |
R4-2015112 |
CR to TS 38.175 on Spatial Exclusion for IAB EMC Radiated Immunity test |
Ericsson |
R4-2017443 |
CR to TS 38.175 on Spatial Exclusion for IAB EMC Radiated Immunity test |
Ericsson |
7.4.7 |
EMC performance requirements [NR_IAB-Perf] |
|
R4-2015028 |
Discussion on the performance requirements of IAB EMC |
ZTE Corporation |
R4-2015113 |
Discussion on IAB EMC performance requirements |
Ericsson |
R4-2015114 |
CR to TS 38.175 on IAB EMC performance requirements |
Ericsson |
R4-2017445 |
WF on IAB EMC test/performance requirements |
ZTE |
R4-2017446 |
CR to TS 38.175 on IAB EMC performance requirements |
Ericsson |
7.4.8.1 |
General [NR_IAB-Perf] |
|
R4-2015868 |
On IAB testing approach |
Ericsson |
R4-2016038 |
IAB Demodulation Testing |
Qualcomm Incorporated |
R4-2016039 |
IAB Demodulation Testing |
Qualcomm Incorporated |
R4-2016443 |
On NR IAB general demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017417 |
Email discussion summary for [97e][319] NR_IAB_Demod |
Moderator (Nokia) |
R4-2017492 |
WF on Rel-16 NR IAB demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017618 |
Email discussion summary for [97e][319] NR_IAB_Demod |
Moderator (Nokia) |
R4-2017673 |
WF on Rel-16 NR IAB demodulation requirements |
Nokia, Nokia Shanghai Bell |
7.4.8.2 |
IAB-DU performance requirements [NR_IAB-Perf] |
|
R4-2015592 |
Discussion on NR IAB DU demodulation performance requirements |
Huawei, HiSilicon |
R4-2015870 |
IAB-DU demodulation requirements |
Ericsson |
R4-2016444 |
On NR IAB-DU demodulation requirements |
Nokia, Nokia Shanghai Bell |
7.4.8.3 |
IAB-MT performance requirements [NR_IAB-Perf] |
|
R4-2015593 |
Discussion on NR IAB MT demodulation performance requirements |
Huawei, HiSilicon |
R4-2015869 |
IAB-MT demodulation requirements |
Ericsson |
R4-2016433 |
On NR IAB-MT test setup and demodulation requirements |
Nokia, Nokia Shanghai Bell |
7.5.1 |
RF requirements maintenance [LTE_NR_DC_CA_enh-Core] |
|
R4-2014229 |
On cell-grouping UE capability for synchronous NR-DC |
Apple |
R4-2014230 |
Reply LS on cell-grouping UE capability for synchronous NR-DC |
Apple |
R4-2014486 |
Draft Reply LS on cell-grouping UE capability for synchronous NR-DC |
Qualcomm Incorporated |
R4-2014958 |
CR to TS 38.101-3 on intra-band contiguous EN-DC BW class (Rel-16) |
ZTE Corporation |
R4-2015036 |
CR to TS 38.307 on the definition of the duplex-mode for the band configurations |
ZTE Corporation, CHTTL |
R4-2015037 |
CR to TS 38.307 on the definition of the duplex-mode for the band configurations |
ZTE Corporation, CHTTL |
R4-2015556 |
Discussion on how to support EN-DC band combinations for Roaming UE |
Huawei, HiSilicon |
R4-2016151 |
Draft Reply LS to RAN2 on cell-grouping UE capability for synchronous NR-DC |
Ericsson GmbH, Eurolab |
R4-2016435 |
Correction to PCMAX for contiguous intra-band EN-DC |
Qualcomm Incorporated |
R4-2016487 |
On UE capability for distinguishing EN-DC implementation capable for different deployment scenarios |
Huawei, HiSilicon |
R4-2016612 |
Email discussion summary for [97e][110] LTE_NR_DC_CA_enh_RF |
Moderator (Ericsson) |
R4-2016812 |
Reply LS on cell-grouping UE capability for synchronous NR-DC |
Apple |
R4-2016845 |
Correction to PCMAX for contiguous intra-band EN-DC |
Qualcomm Incorporated |
R4-2016954 |
Email discussion summary for [97e][110] LTE_NR_DC_CA_enh_RF |
Moderator (Ericsson) |
R4-2017844 |
Reply LS on cell-grouping UE capability for synchronous NR-DC |
Apple |
R4-2017847 |
Reply LS on cell-grouping UE capability for synchronous NR-DC |
RAN4 |
7.5.2 |
RRM core requirements maintenance (38.133/36.133) [LTE_NR_DC_CA_enh-Core] |
|
R4-2014359 |
Discussion on interruption time for unaligned CA scenarios |
MediaTek inc. |
R4-2014360 |
CR on TS38.133 interruption time for CA with non-aligned frame boundaries |
MediaTek inc. |
R4-2017009 |
Email discussion summary for [97e][210] LTE_NR_DC_CA_RRM_1 |
Moderator (Nokia) |
R4-2017010 |
Email discussion summary for [97e][211] LTE_NR_DC_CA_RRM_2 |
Moderator (Ericsson) |
R4-2017118 |
WF on MR-DC RRM requirements for Idle mode CA measurements |
Nokia, Nokia Shanghai Bell |
R4-2017119 |
LS on RAN4 agreements for MR-DC Idle mode CA measurements |
ZTE |
R4-2017123 |
WF on RRM Core requirements maintenance in MR-DC RRM 2 |
Ericsson |
R4-2017124 |
LS on TCI state indication at Direct SCell activation |
MediaTek |
R4-2017128 |
CR on TS38.133 interruption time for CA with non-aligned frame boundaries |
MediaTek inc. |
R4-2017280 |
Email discussion summary for [97e][210] LTE_NR_DC_CA_RRM_1 |
Moderator (Nokia) |
R4-2017281 |
Email discussion summary for [97e][211] LTE_NR_DC_CA_RRM_2 |
Moderator (Ericsson) |
R4-2017329 |
LS on TCI state indication at Direct SCell activation |
RAN4 |
R4-2017330 |
CR on TS38.133 interruption time for CA with non-aligned frame boundaries |
MediaTek inc. |
R4-2017356 |
LS on RAN4 agreements for MR-DC Idle mode CA measurements |
ZTE |
R4-2017357 |
WF on MR-DC RRM requirements for Idle mode CA measurements |
Nokia, Nokia Shanghai Bell |
R4-2017390 |
LS on RAN4 agreements for MR-DC Idle mode CA measurements |
RAN4 |
7.5.2.1 |
Early Measurement reporting [LTE_NR_DC_CA_enh-Core] |
|
R4-2014361 |
Discussion on LTE CRS based and NR SSB based measurement in NR IDLE/INACTIVE mode |
MediaTek inc. |
R4-2014362 |
CR on TS38.133 for measurement capability of IDLE mode DCCA measurement |
MediaTek inc., Huawei, HiSilicon |
R4-2015587 |
Remaining issues on NR EMR |
ZTE |
R4-2015742 |
Discussion on remaining issues in EMR requirements |
Huawei, HiSilicon |
R4-2015743 |
CR on EMR requirements in 36.133 |
Huawei, HiSilicon, MediaTek |
R4-2015881 |
Early Measurement Reporting |
Nokia, Nokia Shanghai Bell |
R4-2015882 |
CR on UE requirement for MR-DC early measurement reporting in 36.133 |
Nokia, Nokia Shanghai Bell |
R4-2015883 |
CR on UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2016388 |
Updates in EMR requirements |
Ericsson |
R4-2016389 |
Updates in EMR requirements |
Ericsson |
R4-2016573 |
Early measurement reporting in MR-DC |
Qualcomm Incorporated |
R4-2017120 |
CR on UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
R4-2017121 |
CR on EMR requirements in 36.133 |
Huawei, HiSilicon, MediaTek |
R4-2017354 |
CR on EMR requirements in 36.133 |
Huawei, HiSilicon, MediaTek |
R4-2017355 |
CR on UE requirement for MR-DC early measurement reporting in 38.133 |
Nokia, Nokia Shanghai Bell |
7.5.2.2 |
Efficient and low latency serving cell configuration, activation and setup [LTE_NR_DC_CA_enh-Core] |
|
R4-2014363 |
Discussion on direct Scell activation |
MediaTek inc. |
R4-2014629 |
Discussion on TCI state activation in direct SCell activation |
MediaTek inc. |
R4-2015301 |
Discussion on RRM requirements for SCell dormancy |
NEC |
R4-2015504 |
CR on BWP switching delay on mulitple CCs |
Huawei, HiSilicon |
R4-2015744 |
Discussion on remaining issues in SCell dormancy and cross-carrier scheduled BWP switching |
Huawei, HiSilicon |
R4-2015745 |
CR on BWP switching and SCell dormancy |
Huawei, HiSilicon |
R4-2016020 |
CR 38.133 Removal of brackets for SCell Dormancy and Direct SCell Activation |
Ericsson |
R4-2016021 |
CR 36.133 Removal of brackets for NR SCell Dormancy |
Ericsson |
R4-2016570 |
Dormant and Non-dormant BWP switching |
Qualcomm Incorporated |
R4-2016575 |
Staring point of an Interruption window at Direct SCell activation |
Qualcomm Incorporated |
R4-2016584 |
CR to Staring point of an Interruption window at Direct SCell activation |
Qualcomm Incorporated |
R4-2017125 |
CR on BWP switching and SCell dormancy |
Huawei, HiSilicon |
R4-2017126 |
CR to Staring point of an Interruption window at Direct SCell activation |
Qualcomm Incorporated |
R4-2017127 |
CR 36.133 Removal of brackets for NR SCell Dormancy |
Ericsson |
R4-2017129 |
CR on BWP switching delay on mulitple CCs |
Huawei, HiSilicon |
R4-2017304 |
CR 38.133 Removal of brackets for SCell Dormancy and Direct SCell Activation |
Ericsson |
7.5.3 |
RRM perf. requirements (38.133) [LTE_NR_DC_CA_enh-Perf] |
|
R4-2017122 |
WF on Test cases for MR-DC Idle mode CA measurements |
Nokia, Nokia Shanghai Bell |
R4-2017130 |
WF on Test Cases for Direct SCell Activation and SCell Dormancy |
Ericsson |
R4-2017358 |
WF on Test cases for MR-DC Idle mode CA measurements |
Nokia, Nokia Shanghai Bell |
R4-2017359 |
Draft Big CR: Introduction of Rel-16 MR-DC EMR RRM performance requirements (TS 38.133) |
Nokia |
R4-2017360 |
Draft Big CR: Introduction of Rel-16 MR-DC EMR RRM performance requirements (TS 36.133) |
Huawei, HiSilicon |
7.5.3.1 |
General [LTE_NR_DC_CA_enh-Perf] |
|
R4-2014368 |
Discussion on performance part for SCell dormancy |
MediaTek inc. |
R4-2015746 |
Discussion on accuracy requirements for EMR |
Huawei, HiSilicon |
R4-2015747 |
draftCR to introduce accuracy requirements for EMR 38.133 |
Huawei, HiSilicon |
R4-2015748 |
draftCR to introduce accuracy for EMR 36.133 |
Huawei, HiSilicon |
R4-2016017 |
General discussion on MR-DC RRM test cases |
Ericsson |
R4-2016378 |
Accuracy requirements for MR-DC EMR (36.133) |
Nokia Corporation |
R4-2016386 |
Accuracy requirements for MR-DC EMR (38.133) |
Nokia Corporation |
R4-2016571 |
Performance requirements for Dormant SCell |
Qualcomm Incorporated |
R4-2017327 |
draftCR to introduce accuracy for EMR 36.133 |
Huawei, HiSilicon |
R4-2017328 |
Accuracy requirements for MR-DC EMR (38.133) |
Nokia Corporation |
R4-2017361 |
Accuracy requirements for MR-DC EMR (38.133) |
Nokia Corporation |
7.5.3.2 |
Test cases [LTE_NR_DC_CA_enh-Perf] |
|
R4-2014369 |
CR on TS38.133 for NR FR1 |
MediaTek inc. |
R4-2015749 |
Discussion on RRM test for MR-DC enhancement |
Huawei, HiSilicon |
R4-2015884 |
Discussion on test cases for MD-DC EMR |
Nokia, Nokia Shanghai Bell |
R4-2016018 |
MR-DC RRM test case list and time plan |
Ericsson |
7.5.4 |
Demodulation and CSI requirements (38.101-4) [LTE_NR_DC_CA_enh-Perf] |
|
R4-2015594 |
Discussion on Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements demodulation performance requirements |
Huawei, HiSilicon |
R4-2015815 |
UE demodulation requirements for WI on MR-DC and CA enhancements |
Ericsson |
R4-2017418 |
Email discussion summary for [97e][320] MR_DC_Demod |
Moderator (Ericsson) |
R4-2017493 |
Way forward on UE demodulation and CSI reporting requirements for MR-DC and CA enhancements |
Ericsson |
7.6 |
UE power saving in NR [NR_UE_pow_sav] |
|
R4-2017011 |
Email discussion summary for [97e][212] NR_UE_pow_sav_RRM |
Moderator (CATT) |
R4-2017282 |
Email discussion summary for [97e][212] NR_UE_pow_sav_RRM |
Moderator (CATT) |
7.6.1 |
RRM core requirements maintenance (38.133) [NR_UE_pow_sav-Core] |
|
R4-2014408 |
CR for TS38.133, Remove duplication definition for measurement requirements for power saving |
CATT |
R4-2014527 |
Discussion on remaining issues of R16 UE power saving |
vivo |
R4-2014528 |
CR on RRM relaxation in R16 UE power saving |
vivo |
R4-2015482 |
Correction CR to Rel-16 UE power saving requirements |
Huawei, HiSilicon |
R4-2015574 |
CR to 38.133: Correction to relaxed measurement requirements |
ZTE |
R4-2016066 |
CR for correcting wrong requirement for UE fulfilling not-at-cell edge criterion for measurement relaxation |
Qualcomm Incorporated |
R4-2016146 |
Corrections to UE power saving requirements |
Ericsson |
R4-2017131 |
Correction CR to Rel-16 UE power saving requirements |
Huawei, HiSilicon |
R4-2017132 |
Corrections to UE power saving requirements |
Ericsson |
7.6.2 |
RRM perf. requirements (38.133) [NR_UE_pow_sav-Perf] |
|
R4-2014455 |
Work plan for power saving RRM test cases |
CATT |
R4-2017133 |
WF on RRM test cases for power saving |
CATT |
R4-2017134 |
Big CR: Introduction of Rel-16 NR UE Power Saving RRM Performance requirements (TS 38.133) |
CATT |
R4-2017135 |
Work plan for power saving RRM test cases |
CATT |
7.6.2.1 |
General [NR_UE_pow_sav-Perf] |
|
R4-2014370 |
Discussion on performance part for cell reselection |
MediaTek inc. |
R4-2014657 |
Discussion on test cases for power saving RRM |
Xiaomi |
R4-2014835 |
Considerations on test cases for UE power saving RRM |
vivo |
R4-2016147 |
Discussions on UE power saving performance requirements |
Ericsson |
7.6.2.2 |
Test cases [NR_UE_pow_sav-Perf] |
|
R4-2014371 |
CR on TS38.133 for cell reselection to FR1 inter-RAT E-UTRA test case with low mobility criterion |
MediaTek inc. |
R4-2014409 |
Discussion on RRM test cases for power saving |
CATT |
R4-2014410 |
CR for TS38.133, test case for cell reselection to FR1 intra-frequency NR case for power saving |
CATT |
R4-2014656 |
RRM test cases for NR UE power saving |
Xiaomi |
R4-2014836 |
CR for test case for cell reselection to FR1 inter-RAT E-UTRA for not at cell edge criterion |
vivo |
R4-2015483 |
Discussion on test cases for measurement relaxation in power saving |
Huawei, HiSilicon |
R4-2015484 |
Test case for cell reselection to FR2 intra-frequency NR case for UE configured with relaxed measurement |
Huawei, HiSilicon |
R4-2016065 |
Draft CR on Cell reselection Tests for UE configured with relaxed measurement criterion |
Qualcomm Incorporated |
R4-2016148 |
Cell reselection to FR2 inter-frequency NR case under power saving |
Ericsson |
R4-2016149 |
Discussions on testing cell reselection to FR2 inter-frequency NR case |
Ericsson |
R4-2017136 |
CR on TS38.133 for cell reselection to FR1 inter-RAT E-UTRA test case with low mobility criterion |
MediaTek inc. |
R4-2017137 |
CR for TS38.133, test case for cell reselection to FR1 intra-frequency NR case for power saving |
CATT |
R4-2017138 |
RRM test cases for NR UE power saving |
Xiaomi |
R4-2017139 |
CR for test case for cell reselection to FR1 inter-RAT E-UTRA for not at cell edge criterion |
vivo |
R4-2017140 |
Test case for cell reselection to FR2 intra-frequency NR case for UE configured with relaxed measurement |
Huawei, HiSilicon |
R4-2017141 |
Draft CR on Cell reselection Tests for UE configured with relaxed measurement criterion |
Qualcomm Incorporated |
R4-2017142 |
Cell reselection to FR2 inter-frequency NR case under power saving |
Ericsson |
R4-2017353 |
Cell reselection to FR2 inter-frequency NR case under power saving |
Ericsson |
7.6.3 |
Demodulation and CSI requirements (38.101-4) [NR_UE_pow_sav-Perf] |
|
R4-2014215 |
Discussion on PDCCH-WUS/PDCCG test |
Apple |
R4-2014411 |
Discussion on power saving demodulation test |
CATT |
R4-2014412 |
CR for TS38.101-4, test for PDCCH DCI format 2_6 demodulation |
CATT |
R4-2014454 |
Work plan for power saving demodulation |
CATT |
R4-2014529 |
Discussion on DCP test cases for R16 UE power saving |
vivo |
R4-2014540 |
Discussion on PDCCH-WUS requirements |
Intel Corporation |
R4-2014727 |
Demodulation on UE power saving |
CMCC |
R4-2015127 |
Discussion on performance requirements for PDCCH-WUS |
MediaTek inc. |
R4-2015595 |
Discussion on the performance requirements for NR power saving |
Huawei, HiSilicon |
R4-2017419 |
Email discussion summary for [97e][321] NR_UE_pow_sav_Demod |
Moderator (CATT) |
R4-2017494 |
WF on power saving demodulation |
CMCC |
R4-2017619 |
Email discussion summary for [97e][321] NR_UE_pow_sav_Demod |
Moderator (CATT) |
R4-2017659 |
Work plan for power saving demodulation |
CATT |
R4-2017677 |
WF on power saving demodulation |
CMCC |
7.7.2 |
RRM core requirements maintenance (38.133) [NR_pos-Core] |
|
R4-2017012 |
Email discussion summary for [97e][213] NR_pos_RRM_1 |
Moderator (Huawei) |
R4-2017143 |
WF on UE PRS measurement requirements |
Huawei, HiSilicon |
R4-2017283 |
Email discussion summary for [97e][213] NR_pos_RRM_1 |
Moderator (Huawei) |
R4-2017372 |
WF on UE PRS measurement requirements |
Huawei, HiSilicon |
7.7.2.1 |
PRS-RSTD measurement requirements [NR_pos-Core] |
|
R4-2014004 |
Measurement period for PRS-RSTD |
ZTE Corporation |
R4-2014445 |
Discussion on PRS RSTD measurement requirements |
CATT |
R4-2014573 |
Further discussion on NR PRS RSTD measurement report requirements |
Intel Corporation |
R4-2014799 |
Further discussion on maintenance for RSTD measurement requirement |
OPPO |
R4-2015750 |
Discussion on remaining issues for RSTD measurement requirements |
Huawei, HiSilicon |
R4-2015751 |
CR to update RSTD measurement requirements |
Huawei, HiSilicon |
R4-2016390 |
On UE positioning measurements: RSTD |
Ericsson |
R4-2016391 |
UE positioning measurements: RSTD |
Ericsson |
R4-2016507 |
PRS-RSTD measurement period requirements |
Qualcomm Incorporated |
R4-2016558 |
Revision of PRS-RSTD measurement period requirements |
Qualcomm Incorporated |
R4-2017144 |
UE positioning measurements: RSTD |
Ericsson |
R4-2017384 |
UE positioning measurements: RSTD |
Ericsson |
7.7.2.2 |
PRS-RSRP measurement requirements [NR_pos-Core] |
|
R4-2014006 |
Requirements for PRS-RSRP measurements |
ZTE Corporation |
R4-2014575 |
Discussion on UE RX-TX time difference measurement requirements |
Intel Corporation |
R4-2015369 |
CR on PRS-RSRP report mapping |
CATT |
R4-2015752 |
Discussison on remaining issues for PRS-RSRP measurement requirements |
Huawei, HiSilicon |
R4-2015753 |
CR to update PRS-RSRP measurement requirements |
Huawei, HiSilicon |
R4-2016392 |
On UE positioning measurements: PRS-RSRP |
Ericsson |
R4-2016393 |
UE positioning measurements: PRS-RSRP |
Ericsson |
R4-2016557 |
Revision of PRS-RSRP measurement period requirements |
Qualcomm Incorporated |
R4-2017145 |
CR to update PRS-RSRP measurement requirements |
Huawei, HiSilicon |
R4-2017146 |
CR on PRS-RSRP report mapping |
CATT |
7.7.2.3 |
UE Rx-Tx time difference measurement requirements [NR_pos-Core] |
|
R4-2014003 |
UE Rx-Tx measurements |
ZTE Corporation |
R4-2014446 |
Discussion on UE Rx-Tx time difference measurement requirements |
CATT |
R4-2015754 |
Discussison on remaining issues for UE Rx-Rx time difference measurement requirements |
Huawei, HiSilicon |
R4-2015755 |
CR to update UE Rx-Tx time difference measurement requirements |
Huawei, HiSilicon |
R4-2016394 |
On UE positioning measurements: UE Rx-Tx |
Ericsson |
R4-2016395 |
UE positioning measurements: UE Rx-Tx |
Ericsson |
R4-2016508 |
UE Rx-Tx time difference measurement period requirements |
Qualcomm Incorporated |
R4-2016559 |
Revision of UE Rx-Tx time difference measurement period requirements and applicability |
Qualcomm Incorporated |
7.7.2.4 |
Other requirements [NR_pos-Core] |
|
R4-2014005 |
New gap patterns for PRS measurements |
ZTE Corporation |
R4-2014282 |
LS on new per-UE MG for NR positioning |
RAN4 |
R4-2014798 |
CR to TS 38.133 on measurement period requirements for PRS RSTD, PRS-RSRP and UE Rx-Tx(section 9.9) |
OPPO |
R4-2015756 |
Discussion on remaining issues in CSSF for PRS measurement |
Huawei, HiSilicon |
R4-2015757 |
CR on CSSF for PRS measurement |
Huawei, HiSilicon |
R4-2015758 |
CR to introduce new measurement gap patterns for positioning in 36.133 |
Huawei, HiSilicon |
R4-2016156 |
Refinements on CSSF within gap to include NR positioning measurements |
Nokia, Nokia Shanghai Bell |
R4-2016396 |
On CSSF for positioning measurements |
Ericsson |
R4-2016397 |
Correction to CSSF for positioning measurements |
Ericsson |
R4-2016505 |
General NR positioning measurement requirements |
Qualcomm Incorporated |
R4-2016556 |
Revision of NR positioning measurement requirements applicability |
Qualcomm Incorporated |
R4-2016999 |
CR to TS 38.133 on measurement period requirements for PRS RSTD, PRS-RSRP and UE Rx-Tx(section 9.9) |
OPPO |
R4-2017147 |
CR to TS 38.133 on measurement period requirements for PRS RSTD, PRS-RSRP and UE Rx-Tx(section 9.9) |
OPPO |
R4-2017148 |
CR to introduce new measurement gap patterns for positioning in 36.133 |
Huawei, HiSilicon |
R4-2017149 |
Revision of NR positioning measurement requirements applicability |
Qualcomm Incorporated |
R4-2017150 |
Refinements on CSSF within gap to include NR positioning measurements |
Nokia, Nokia Shanghai Bell |
7.7.3 |
RRM perf. requirements (38.133) [NR_pos-Perf] |
|
R4-2017013 |
Email discussion summary for [97e][214] NR_pos_RRM_2 |
Moderator (Intel Corporation) |
R4-2017151 |
WF on UE PRS performance requirements |
Intel Corporation |
R4-2017284 |
Email discussion summary for [97e][214] NR_pos_RRM_2 |
Moderator (Intel Corporation) |
R4-2017371 |
WF on UE PRS performance requirements |
Intel Corporation |
7.7.3.1 |
General [NR_pos-Perf] |
|
R4-2014571 |
Discussion on NR Positioning test cases configuration and list |
Intel Corporation |
R4-2014572 |
Draft CR to TS 38.133: PRS configurations for NR Pos RRM tests |
Intel Corporation |
R4-2015567 |
Work plan for NR Positioning RRM Performance part |
Intel Corporation |
R4-2016398 |
General discussion on NR RRM positioning test cases |
Ericsson |
R4-2017156 |
Draft CR to TS 38.133: PRS configurations for NR Pos RRM tests |
Intel Corporation |
R4-2017158 |
Work plan for NR Positioning RRM Performance part |
Intel Corporation |
R4-2017373 |
Draft Big CR: Introduction of Rel-16 NR Positioning RRM performance requirements and test cases (TS 38.133) |
Ericsson, Intel |
7.7.3.2.1.1 |
PRS RSTD [NR_pos-Perf] |
|
R4-2014447 |
Discussion on PRS RSTD accuracy requirements |
CATT |
R4-2014450 |
CR on PRS RSTD accuracy requirements |
CATT |
R4-2014574 |
Discussion on NR PRS RSTD Measurement Accuracy Requirements |
Intel Corporation |
R4-2015759 |
Discussion on accuracy requirements for RSTD measurement |
Huawei, HiSilicon |
R4-2015760 |
draftCR to introduce accuracy requirements for RSTD measurement |
Huawei, HiSilicon |
R4-2016404 |
On RSTD measurement accuracy |
Ericsson |
R4-2016405 |
RSTD measurement accuracy |
Ericsson |
R4-2016510 |
PRS-RSTD measurement accuracy requirements |
Qualcomm Incorporated |
R4-2017153 |
draftCR to introduce accuracy requirements for RSTD measurement |
Huawei, HiSilicon |
7.7.3.2.1.2 |
PRS RSRP [NR_pos-Perf] |
|
R4-2014007 |
Accuracy requirements for PRS-RSRP measurements |
ZTE Corporation |
R4-2014448 |
Discussion on PRS RSRP accuracy requirements |
CATT |
R4-2014451 |
CR on PRS-RSRP accuracy requirements |
CATT |
R4-2014578 |
Discussion on PRS RSRP accuracy requirements for NR Positioning |
Intel Corporation |
R4-2014579 |
Link-level simulation results for PRS RSRP measurement |
Intel Corporation |
R4-2015761 |
Discussion on accuracy requirements for PRS-RSRP measurement |
Huawei, HiSilicon |
R4-2015762 |
draftCR to introduce accuracy requirements for PRS-RSRP measurement |
Huawei, HiSilicon |
R4-2016402 |
On PRS-RSRP measurement accuracy |
Ericsson |
R4-2016403 |
PRS-RSRP measurement accuracy |
Ericsson |
R4-2016509 |
PRS-RSRP measurement accuracy requirements |
Qualcomm Incorporated |
R4-2017154 |
CR on PRS-RSRP accuracy requirements |
CATT |
7.7.3.2.1.3 |
UE Rx-Tx time difference [NR_pos-Perf] |
|
R4-2014449 |
Discussion on UE Rx-Tx time difference accuracy requirements |
CATT |
R4-2014452 |
CR on UE Rx-Tx time difference accuracy requirements |
CATT |
R4-2014576 |
Discussion on UE RX-TX time difference measurement accuracy requirements |
Intel Corporation |
R4-2014577 |
Link-level simulation results for UE RX-TX time difference measurement |
Intel Corporation |
R4-2015763 |
Discussion on accuracy requirements for UE Rx-Tx time difference measurement |
Huawei, HiSilicon |
R4-2015764 |
draftCR to introduce accuracy requirements for UE Rx-Tx time difference measurement |
Huawei, HiSilicon |
R4-2016406 |
On UE Rx-Tx measurement accuracy |
Ericsson |
R4-2016407 |
UE Rx-Tx measurement accuracy |
Ericsson |
R4-2016511 |
UE Rx-Tx time difference measurement accuracy requirements |
Qualcomm Incorporated |
R4-2017155 |
UE Rx-Tx measurement accuracy |
Ericsson |
7.7.3.2.2 |
Test cases [NR_pos-Perf] |
|
R4-2015370 |
CR on conditions for NR RSTD measurement |
CATT |
R4-2015765 |
Discussion on RRM test case for UE positioning requirements |
Huawei, HiSilicon |
R4-2015766 |
draftCR on PRS RMC for positioning test cases |
Huawei, HiSilicon |
R4-2016399 |
NR RRM positioning test cases list and time plan |
Ericsson |
R4-2016400 |
NR RRM positioning test cases structure |
Ericsson |
R4-2017152 |
NR RRM positioning test cases structure |
Ericsson |
R4-2017157 |
CR on conditions for NR RSTD measurement |
CATT, Ericsson |
7.7.3.2.3 |
Other [NR_pos-Perf] |
|
R4-2016401 |
Correction to UE Rx-Tx measurement report mapping |
Ericsson |
7.7.3.3 |
gNB requirements [NR_pos-Perf] |
|
R4-2014002 |
gNB requirements for NR positioning |
ZTE Corporation |
R4-2014453 |
Discussion on gNB measurement requirements |
CATT |
R4-2015767 |
Discussion on the scope gNB requirements for NR positioning |
Huawei, HiSilicon, CMCC |
R4-2015768 |
Discussion on gNB positioning measurement requirements |
Huawei, HiSilicon |
R4-2015769 |
System and link level simulation results for gNB measurement requirements |
Huawei, HiSilicon |
R4-2015770 |
draftCR to introduce accuracy requirements for gNB positioning measurement |
Huawei, HiSilicon |
R4-2016062 |
gNB timing positioning measurement report mapping update for k |
Ericsson |
R4-2016088 |
gNB Positioning Requirements |
Ericsson |
R4-2016109 |
gNB Positioning UL SRS System Simulation Results |
Ericsson |
R4-2016154 |
gNB Positioning UL SRS Link Level Simulation Results |
Ericsson |
R4-2016157 |
On gNB measurement accuracy requirements for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2016158 |
System simulation results for SRS for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2016159 |
System simulation results for SRS for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2016506 |
gNB requirements for positioning |
Qualcomm Incorporated |
R4-2017014 |
Email discussion summary for [97e][215] NR_pos_RRM_3 |
Moderator (Ericsson) |
R4-2017159 |
WF on gNB positioning measurement requirements |
Ericsson |
R4-2017160 |
Updated system simulation assumptions on gNB positioning measurement for deriving side conditions |
Ericsson |
R4-2017161 |
gNB timing positioning measurement report mapping update for k |
Ericsson |
R4-2017285 |
Email discussion summary for [97e][215] NR_pos_RRM_3 |
Moderator (Ericsson) |
R4-2017370 |
Updated system simulation assumptions on gNB positioning measurement for deriving side conditions |
Ericsson |
R4-2017385 |
Updated system simulation assumptions on gNB positioning measurement for deriving side conditions |
Ericsson |
7.8.1.1 |
Performance requirements with ultra-low BLER [NR_L1enh_URLLC-Perf] |
|
R4-2017420 |
Email discussion summary for [97e][322] NR_URLLC_Demod_Part1 |
Moderator (Ericsson) |
R4-2017507 |
WF on ultra-low BLER requirements |
Ericsson |
R4-2017508 |
LS to RAN5 on CQI reporting for URLLC |
Qualcomm |
R4-2017620 |
Email discussion summary for [97e][322] NR_URLLC_Demod_Part1 |
Moderator (Ericsson) |
R4-2017674 |
WF on ultra-low BLER requirements |
Ericsson |
7.8.1.1.1 |
UE demodulation requirements [NR_L1enh_URLLC-Perf] |
|
R4-2014241 |
UE demodulation requirements for Ultra low BLER |
Apple |
R4-2014541 |
Simulation results for Ultra-low BLER UE demodulation requirements |
Intel Corporation |
R4-2015622 |
CR to TS 38.101-4: Applicability rules for URLLC UE demodulation requirements |
Huawei, HiSilicon |
R4-2015862 |
Summary of ideal and impairment results for ultra-low BLER UE |
Ericsson |
R4-2016004 |
CR on FRC for UE Ultra-low BLER requirements |
Intel Corporation |
R4-2016105 |
Simulation results on UE URLLC demodulation performance requirements for Ultra low BLER |
Ericsson |
R4-2016107 |
CR to TS 38.101-4: Performance requirements for URLLC PDSCH 0.001% BLER |
Ericsson |
R4-2017495 |
Summary of ideal and impairment results for ultra-low BLER UE |
Ericsson |
R4-2017496 |
CR on FRC for UE Ultra-low BLER requirements |
Intel Corporation |
R4-2017497 |
CR to TS 38.101-4: Performance requirements for URLLC PDSCH 0.001% BLER |
Ericsson |
R4-2017515 |
CR to TS 38.101-4: Applicability rules for URLLC UE demodulation requirements |
Huawei, HiSilicon |
7.8.1.1.2 |
CSI requirements [NR_L1enh_URLLC-Perf] |
|
R4-2014542 |
Discussion on CSI requirements for Ultra-low BLER |
Intel Corporation |
R4-2015615 |
Discussion on CSI requireements with ultra low-BLER |
Huawei, HiSilicon |
R4-2015621 |
CR to TS 38.101-4: Applicability rules for URLLC CSI requirements |
Huawei, HiSilicon |
R4-2015863 |
On 0.001%BLER CQI test |
Ericsson |
R4-2015864 |
Simulation results on URLLC UE CQI reporting requirements for CQI table 3 |
Ericsson |
R4-2016375 |
Draft CR on CQI reporting requirements with Table 3 |
Apple |
R4-2016376 |
Draft CR on Applicability of CQI reporting requirements with Table 3 |
Apple |
R4-2016445 |
Views on URLLC Ultra-low BLER CSI Reporting Test Cases |
Qualcomm Incorporated |
R4-2017498 |
CR to TS 38.101-4: Applicability rules for URLLC CSI requirements |
Huawei, HiSilicon |
R4-2017499 |
Draft CR on CQI reporting requirements with Table 3 |
Apple |
7.8.1.1.3 |
BS demodulation requirements [NR_L1enh_URLLC-Perf] |
|
R4-2014543 |
Simulation results for Ultra-low BLER BS requirements |
Intel Corporation |
R4-2015024 |
Test requirements for 0.001% BLER |
Ericsson |
R4-2015025 |
Introduction of URLLC 0.001% BLER requirement |
Ericsson |
R4-2015094 |
On NR Rel-16 BS demodulation performance requirements with ultra-low BLER |
Nokia, Nokia Shanghai Bell |
R4-2015096 |
CR for 38.104: Ultra high reliability BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2015098 |
CR for 38.141-1: URLLC testing methodology appendix |
Nokia, Nokia Shanghai Bell, Intel, Ericsson, Huawei, HiSilicon |
R4-2015099 |
CR for 38.141-2: URLLC testing methodology appendix |
Nokia, Nokia Shanghai Bell, Intel, Ericsson, Huawei, HiSilicon |
R4-2015625 |
CR to TS 38.141-1: Applicability of URLLC BS demodulation requirements |
Huawei, HiSilicon |
R4-2015627 |
CR to TS 38.141-2: FRC for FR1 URLLC BS performance requirements |
Huawei, HiSilicon |
R4-2015861 |
Summary of ideal and impairment results for ultra-low BLER BS |
Ericsson |
R4-2015867 |
Base station ultra-low BLER simulation results |
Ericsson |
R4-2017500 |
Summary of ideal and impairment results for ultra-low BLER BS |
Ericsson |
R4-2017501 |
Test requirements for 0.001% BLER |
Ericsson |
R4-2017502 |
Introduction of URLLC 0.001% BLER requirement |
Ericsson |
R4-2017503 |
CR for 38.104: Ultra high reliability BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017504 |
CR for 38.141-1: URLLC testing methodology appendix |
Nokia, Nokia Shanghai Bell, Intel, Ericsson, Huawei, HiSilicon |
R4-2017505 |
CR for 38.141-2: URLLC testing methodology appendix |
Nokia, Nokia Shanghai Bell, Intel, Ericsson, Huawei, HiSilicon |
R4-2017506 |
CR to TS 38.141-2: FRC for FR1 URLLC BS performance requirements |
Huawei, HiSilicon |
R4-2017521 |
CR to TS 38.141-1: Applicability of URLLC BS demodulation requirements |
Huawei, HiSilicon |
7.8.1.2 |
Performance requirements with higher BLER [NR_L1enh_URLLC-Perf] |
|
R4-2017421 |
Email discussion summary for [97e][323] NR_URLLC_Demod_Part2 |
Moderator (Huawei) |
R4-2017509 |
WF on URLLC UE performance requirements with higher BLER |
Intel |
R4-2017510 |
Simulation assumption for URLLC FR2 UE performance requirements with higher BLER |
Intel |
R4-2017525 |
WF on URLLC BS performance requirement with higher BLER |
Huawei |
R4-2017526 |
Simulation assumption for URLLC FR2 BS performance requirement with higher BLER |
Huawei |
R4-2017621 |
Email discussion summary for [97e][323] NR_URLLC_Demod_Part2 |
Moderator (Huawei) |
R4-2017675 |
WF on URLLC BS performance requirement with higher BLER |
Huawei |
7.8.1.2.1 |
UE demodulation requirements [NR_L1enh_URLLC-Perf] |
|
R4-2014242 |
UE demodulation requirements with higher BLER |
Apple |
R4-2014243 |
CR on requirements with slot aggreagation in FR2 |
Apple |
R4-2014544 |
Discussion on UE demodulation requirements for URLLC |
Intel Corporation |
R4-2015129 |
Discussion on eMBB UE performance requirement with pre-emption |
MediaTek inc. |
R4-2015616 |
Simulation results on UE PDSCH demodulation reuqirements with higher BLER and low latency |
Huawei, HiSilicon |
R4-2015617 |
Discussion on URLLC UE demodulation requirements with higher BLER and low latency |
Huawei, HiSilicon |
R4-2015620 |
CR to TS 38.101-4: Addition of UE performance requirements for FR1 URLLC PDSCH repetitions over multiple slots |
Huawei, HiSilicon |
R4-2015628 |
Summary of simulation results for UE URLLC demodulation performance requirements |
Huawei, HiSilicon |
R4-2016005 |
CR on FRC for UE Higher BLER requirements |
Intel Corporation |
R4-2016103 |
Discussion on UE URLLC demodulation performance requirements with higher BLER |
Ericsson |
R4-2016104 |
Simulation results on UE URLLC demodulation performance requirements with higher BLER |
Ericsson |
R4-2016106 |
CR to TS 38.101-4: Performance requirements for URLLC High BLER feature tests |
Ericsson |
R4-2016462 |
Views on URLLC High BLER Demodulation Test Cases |
Qualcomm Incorporated |
R4-2016504 |
CR on FR1 PDSCH Mapping Type B and Processing Capability 2 Requirements |
Qualcomm Incorporated |
R4-2017511 |
CR to TS 38.101-4: Addition of UE performance requirements for FR1 URLLC PDSCH repetitions over multiple slots |
Huawei, HiSilicon |
R4-2017512 |
CR on FRC for UE Higher BLER requirements |
Intel Corporation |
R4-2017513 |
CR to TS 38.101-4: Performance requirements for URLLC High BLER feature tests |
Ericsson |
R4-2017514 |
CR on requirements with slot aggregation in FR2 |
Apple |
R4-2017516 |
CR on FR1 PDSCH Mapping Type B and Processing Capability 2 Requirements |
Qualcomm Incorporated |
R4-2017665 |
CR on FR1 PDSCH Mapping Type B and Processing Capability 2 Requirements |
Qualcomm Incorporated |
7.8.1.2.2 |
BS demodulation requirements [NR_L1enh_URLLC-Perf] |
|
R4-2014545 |
Discussion on BS demodulation requirements for URLLC |
Intel Corporation |
R4-2014820 |
CR for TS 38.141-2: Introduction of performance requirements of PUSCH repetition type A and PUSCH mapping type B for URLLC |
NTT DOCOMO, INC. |
R4-2014821 |
Views on NR BS performance for high-reliability and low-latency |
NTT DOCOMO, INC. |
R4-2015023 |
FRCs for URLLC |
Ericsson |
R4-2015095 |
On NR Rel-16 BS demodulation performance requirements with higher BLER and simulation results |
Nokia, Nokia Shanghai Bell |
R4-2015097 |
CR for 38.104: Low latency BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2015122 |
Discussion and simulation results for BS URLLC requirement |
Samsung |
R4-2015123 |
Draft CR on PUSCH repetition type A and PUSCH mapping type B radiated performance requirement for TS 38.104 |
Samsung |
R4-2015124 |
Draft CR on FRC for URLLC BS radiated performance requirement for TS 38.141-2 |
Samsung |
R4-2015618 |
Discussion on URLLC BS demodulation requirements with higher BLER and low latency |
Huawei, HiSilicon |
R4-2015619 |
Simulation results on PUSCH demodulation reuqirements with higher BLER and low latency |
Huawei, HiSilicon |
R4-2015623 |
CR to TS 38.104: Addition of BS performance requirements for URLLC PUSCH repetition Type A |
Huawei, HiSilicon |
R4-2015624 |
CR to TS 38.141-1: Addition of BS conformance testing for URLLC demodulation requirements with higher BLER |
Huawei, HiSilicon |
R4-2015626 |
CR to TS 38.141-2: Addition of BS conformance testing for FR2 URLLC PUSCH repetition Type A |
Huawei, HiSilicon |
R4-2015629 |
Summary of simulation results for BS URLLC demodulation performance requirements |
Huawei, HiSilicon |
R4-2015865 |
BS demodulation parameters |
Ericsson |
R4-2015866 |
Simulation results for BS high BLER URLLC |
Ericsson |
R4-2016006 |
CR on FR2 requirements for PUSCH mapping Type B with low number of symbols |
Intel Corporation |
R4-2017517 |
CR for TS 38.141-2: Introduction of performance requirements of PUSCH repetition type A and PUSCH mapping type B for URLLC |
NTT DOCOMO, INC. |
R4-2017518 |
FRCs for URLLC |
Ericsson |
R4-2017519 |
Draft CR on PUSCH repetition type A and PUSCH mapping type B radiated performance requirement for TS 38.104 |
Samsung |
R4-2017520 |
Draft CR on FRC for URLLC BS radiated performance requirement for TS 38.141-2 |
Samsung |
R4-2017522 |
CR to TS 38.141-2: Addition of BS conformance testing for FR2 URLLC PUSCH repetition Type A |
Huawei, HiSilicon, NTT DoCoMo |
R4-2017523 |
CR on FR2 requirements for PUSCH mapping Type B with low number of symbols |
Intel Corporation, NTT DoCoMo |
R4-2017524 |
CR for 38.104: Low latency BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017527 |
CR to TS 38.104: Addition of BS performance requirements for URLLC PUSCH repetition Type A |
Huawei, HiSilicon |
R4-2017528 |
CR to TS 38.141-1: Addition of BS conformance testing for URLLC demodulation requirements with higher BLER |
Huawei, HiSilicon |
7.9.1 |
UE RF core requirements maintenance (38.101) [NR_eMIMO-Core] |
|
R4-2016613 |
Email discussion summary for [97e][111] NR_eMIMO_UE_RF |
Moderator (Samsung) |
R4-2016955 |
Email discussion summary for [97e][111] NR_eMIMO_UE_RF |
Moderator (Samsung) |
7.9.1.1 |
DMRS enhancement with PI/2 BPSK [NR_eMIMO-Core] |
|
R4-2016481 |
CR for TS 38.101-1: correction of Pi/2 BPSK |
Huawei, HiSilicon |
R4-2016813 |
CR for TS 38.101-1: correction of Pi/2 BPSK |
Huawei, HiSilicon |
7.9.1.2 |
Uplink Tx Full Power transmission [NR_eMIMO-Core] |
|
R4-2016480 |
On MPR for TxD and UL MIMO |
Huawei, HiSilicon |
7.9.2 |
RRM core requirements maintenance (38.133) [NR_eMIMO-Core] |
|
R4-2014244 |
Discussion on RRM requirements for Multi-TRP |
Apple |
R4-2014245 |
CR to 38.133 on RRM requirements for multi-TRxP |
Apple |
R4-2014246 |
CR to 38.133 on Link recovery requirements |
Apple |
R4-2015826 |
CR: Clarification of L1-SINR reporting with CSI-RS based CMR and dedicated IMR configured |
Ericsson |
R4-2016029 |
DraftCR to TS38.133 on L1-SINR Measurement Requirement |
Samsung |
R4-2017015 |
Email discussion summary for [97e][216] NR_eMIMO_RRM |
Moderator (Samsung) |
R4-2017165 |
CR: Clarification of L1-SINR reporting with CSI-RS based CMR and dedicated IMR configured |
Ericsson |
R4-2017286 |
Email discussion summary for [97e][216] NR_eMIMO_RRM |
Moderator (Samsung) |
7.9.3 |
RRM perf. requirements (38.133) [NR_eMIMO-Perf] |
|
R4-2017164 |
WF on NR eMIMO RRM Performance requirements |
Samsung |
R4-2017375 |
WF on NR eMIMO RRM Performance requirements |
Samsung |
R4-2017376 |
Draft Big CR: Introduction of Rel-16 NR eMIMO RRM performance requirements and test cases |
Samsung |
7.9.3.1 |
General [NR_eMIMO-Perf] |
|
R4-2014756 |
Discussion on RRM Performance part for Rel-16 NR eMIMO |
Samsung |
7.9.3.2 |
L1-SINR measurement accuracy [NR_eMIMO-Perf] |
|
R4-2014247 |
Simulation results for L1-SINR Measurement accuracy |
Apple |
R4-2014297 |
Requirements for L1-SINR measurement accuracy |
Qualcomm CDMA Technologies |
R4-2014603 |
Discussion on L1-SINR measurement accuracy requirement |
MediaTek inc. |
R4-2014758 |
Simulation results summary for L1-SINR measurement accuracy |
Samsung |
R4-2014759 |
Discussion on L1-SINR measurement accuracy requirement |
Samsung |
R4-2015471 |
Discussion on L1-SINR measurement accuracy requirements |
Huawei, HiSilicon |
R4-2016239 |
Simulation results of L1-SINR measurement accuracy |
Nokia, Nokia Shanghai Bell |
R4-2016240 |
CR to TS 38.133: Adding L1-SINR accuracy requirements |
Nokia, Nokia Shanghai Bell |
R4-2017166 |
CR to TS 38.133: Adding L1-SINR accuracy requirements |
Nokia, Nokia Shanghai Bell |
7.9.3.3.1 |
L1-SINR measurements [NR_eMIMO-Perf] |
|
R4-2014291 |
Draft test case CR on measurement procedure of L1-SINR for CSI-RS-based CMR and no dedicated IMR |
Qualcomm CDMA Technologies |
R4-2014604 |
Discussion on test cases for L1-SINR measurement |
MediaTek inc. |
R4-2014757 |
DraftCR on L1-SINR measurement test case with CSI-RS CMR and dedicated IMR |
Samsung |
R4-2015472 |
Discussion on L1-SINR measurement tests for NR eMIMO |
Huawei, HiSilicon |
R4-2015473 |
DraftCR on L1-SINR measurement procedure tests with SSB based CMR and dedicated IMR |
Huawei, HiSilicon |
R4-2015827 |
Simulation results of L1-SINR measurement accuracy |
Ericsson |
R4-2017167 |
Draft test case CR on measurement procedure of L1-SINR for CSI-RS-based CMR and no dedicated IMR |
Qualcomm CDMA Technologies |
R4-2017168 |
DraftCR on L1-SINR measurement test case with CSI-RS CMR and dedicated IMR |
Samsung |
R4-2017169 |
DraftCR on L1-SINR measurement procedure tests with SSB based CMR and dedicated IMR |
Huawei, HiSilicon |
7.9.3.3.2 |
BFR for SCell [NR_eMIMO-Perf] |
|
R4-2014605 |
Discussion on test cases for SCell BFR |
MediaTek inc. |
R4-2014606 |
Introduction of test cases for BFD and link recovery procedure for Scell |
MediaTek inc. |
R4-2015828 |
Link recovery test with link recovery requests |
Ericsson |
R4-2015829 |
Draft CR: Introduction of test case of link recovery with link recovery requests |
Ericsson |
R4-2017170 |
Introduction of test cases for BFD and link recovery procedure for Scell |
MediaTek inc. |
R4-2017171 |
Draft CR: Introduction of test case of link recovery with link recovery requests |
Ericsson |
7.9.3.3.3 |
DL/UL beam indication with reduced latency and overhead [NR_eMIMO-Perf] |
|
R4-2014010 |
Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation |
R4-2014011 |
[draft CR] Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation |
7.9.3.3.4 |
Others [NR_eMIMO-Perf] |
|
R4-2014292 |
Draft test case CR on measurement performance of L1-SINR for CSI-RS-based CMR and no dedicated IMR |
Qualcomm CDMA Technologies |
R4-2015474 |
DraftCR on L1-SINR measurement accuracy tests with SSB based CMR and dedicated IMR |
Huawei, HiSilicon |
7.9.4.1 |
General [NR_eMIMO-Perf] |
|
R4-2014248 |
Draft CR for eMIMO demod requirements - General and Applicability rule |
Apple |
R4-2014741 |
Views for Multi-Panel/TRP transmision schemes |
Samsung |
R4-2014742 |
Simulation results summary for Rel-16 eMIMO WI |
Samsung |
R4-2017422 |
Email discussion summary for [97e][324] NR_eMIMO_Demod |
Moderator (Samsung) |
R4-2017529 |
WF for NR eMIMO PDSCH requirement |
Intel |
R4-2017530 |
Simulation assumption for PDSCH requirement with single-DCI and Multi-DCI transmission schemes |
Ericsson, Intel |
R4-2017531 |
Way forward on PMI reporting requirement for NR eMIMO |
Ericsson, Samsung |
R4-2017601 |
Draft CR for eMIMO demod requirements - General and Applicability rule |
Apple |
R4-2017622 |
Email discussion summary for [97e][324] NR_eMIMO_Demod |
Moderator (Samsung) |
R4-2017678 |
Way forward on PMI reporting requirement for NR eMIMO |
Ericsson, Samsung |
7.9.4.2 |
Demodulation requirements [NR_eMIMO-Perf] |
|
R4-2015830 |
Draft CR: PDSCH FRC for eMIMO sDCI/mDCI-based SDM transmission |
Ericsson |
R4-2017650 |
Draft CR: PDSCH FRC for eMIMO sDCI/mDCI-based SDM transmission |
Ericsson |
7.9.4.2.1 |
Single-DCI based SDM scheme [NR_eMIMO-Perf] |
|
R4-2014557 |
Views on UE demodulation requirements for single-DCI based multi-TRP SDM Tx scheme |
Intel Corporation |
R4-2014743 |
Simulation results for Single-DCI SDM scheme |
Samsung |
R4-2015650 |
Simulaiton results of PDSCH requirements for Single-DCI SDM scheme |
Huawei, HiSilicon |
R4-2015653 |
DraftCR for 38.101-4: Introduction of PDSCH requirement with Single-DCI based SDM scheme |
Huawei, HiSilicon |
R4-2015831 |
Simulation results of single-DCI based SDM transmission |
Ericsson |
R4-2017532 |
DraftCR for 38.101-4: Introduction of PDSCH requirement with Single-DCI based SDM scheme |
Huawei, HiSilicon |
7.9.4.2.2 |
Multi-DCI based transmission scheme [NR_eMIMO-Perf] |
|
R4-2014556 |
Views on UE demodulation requirements for multi-DCI based multi-TRP Tx schemes |
Intel Corporation |
R4-2014744 |
Simulation results for Multi-DCI transmission schemes |
Samsung |
R4-2015128 |
Simulation results on PDSCH performance requirements for multi-DCI based multi-TRP transmission |
MediaTek inc. |
R4-2015648 |
Discussion on left open issues of PDSCH performance requirements for multi/single-DCI transmission scheme |
Huawei, HiSilicon |
R4-2015649 |
Simulation results of PDSCH requirements for Multi-DCI transmission scheme |
Huawei, HiSilicon |
R4-2015654 |
DraftCR for 38.101-4: Introduction of PDSCH requirement with Multi-DCI based transmission scheme |
Huawei, HiSilicon |
R4-2015832 |
PDSCH requirements for mDCI/sDCI-based SDM transmission |
Ericsson |
R4-2015833 |
Simulation results of multi-DCI based SDM transmission |
Ericsson |
R4-2017533 |
DraftCR for 38.101-4: Introduction of PDSCH requirement with Multi-DCI based transmission scheme |
Huawei, HiSilicon |
7.9.4.2.3 |
Single-DCI based transmission schemes (URLLC) [NR_eMIMO-Perf] |
|
R4-2014558 |
Views on UE demodulation requirements for single-DCI based multi-TRP Repetition Tx schemes |
Intel Corporation |
R4-2014559 |
CR to TS 38.101-4: Performance requirements single-DCI based multi-TRP Repetition Tx schemes |
Intel Corporation |
R4-2014745 |
Simulation results for Single-DCI URLLC schemes |
Samsung |
R4-2015651 |
Discussion on PDSCH performance reuqirements for Multi-TRP URLLC schemes |
Huawei, HiSilicon |
R4-2015652 |
Simulation results of PDSCH requirements for Single-DCI URLLC schemes |
Huawei, HiSilicon |
R4-2015834 |
Discussion on sDCI-based FDM/TDM transmission schemes |
Ericsson |
R4-2017534 |
CR to TS 38.101-4: Performance requirements single-DCI based multi-TRP Repetition Tx schemes |
Intel Corporation |
7.9.4.3 |
CSI requirements [NR_eMIMO-Perf] |
|
R4-2014249 |
On PMI reporting requirements with eType II codebook |
Apple |
R4-2014740 |
Views and simulation results for Rel-16 Type II PMI test case |
Samsung |
R4-2014747 |
Draft CR for introduction of Rel-15 Type II PMI test cases |
Samsung |
R4-2014949 |
On PMI reporting requirements for enhanced Type II codebooks |
Nokia, Nokia Shanghai Bell |
R4-2015646 |
Discussion on the test setup of (e)Type II codebook based PMI reporting test |
Huawei, HiSilicon |
R4-2015647 |
Simulation results for SU-MIMO eType II codebook based PMI reporting test |
Huawei, HiSilicon |
R4-2016033 |
Discussion on Type II PMI reporting test definition |
Rohde & Schwarz |
R4-2016101 |
Simulation results for Rel-16 Type II codebook |
Ericsson |
R4-2016102 |
Evaluations of Rel-16 Type II PMI testing |
Ericsson |
R4-2016429 |
Views on CSI Reporting test cases for eMIMO |
Qualcomm Incorporated |
R4-2017535 |
Draft CR for introduction of Rel-15 Type II PMI test cases |
Samsung |
7.10.1 |
Demodulation and CSI requirements (38.101-4) [NR_DL256QAM_FR2-Perf] |
|
R4-2017423 |
Email discussion summary for [97e][325] NR_DL256QAM_FR2_Demod |
Moderator (China Telecomm) |
R4-2017536 |
WF on UE demodulation and CSI reporting requirements for FR2 DL 256QAM |
China Telecomm |
R4-2017623 |
Email discussion summary for [97e][325] NR_DL256QAM_FR2_Demod |
Moderator (China Telecomm) |
7.10.1.1 |
UE Demodulation requirements [NR_DL256QAM_FR2-Perf] |
|
R4-2014546 |
Discussion on UE demodulation requirements for FR2 DL 256QAM |
Intel Corporation |
R4-2014547 |
Summary of simulation results FR2 DL 256QAM demodulation requirements |
Intel Corporation |
R4-2014674 |
Updated work plan for FR2 DL 256QAM demodulation and CSI reporting requirements |
China Telecom |
R4-2014675 |
On UE demodulation requirements for FR2 DL 256QAM |
China Telecom |
R4-2015019 |
Propagation Condition for FR2 DL 256QAM |
ZTE Corporation |
R4-2015021 |
CR to demodulation performance requirements |
ZTE Corporation |
R4-2015314 |
Views on 256QAM UE requirements for FR2 |
NTT DOCOMO, INC. |
R4-2015596 |
CR on applicability and FRC for PDSCH normal demodulation for DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2015597 |
Discussion on PDSCH requirements for NR DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2016095 |
Simulation results for FR2 256QAM UE demodulation |
Ericsson |
R4-2017537 |
CR to demodulation performance requirements |
ZTE Corporation |
7.10.1.2 |
SDR requirements [NR_DL256QAM_FR2-Perf] |
|
R4-2014548 |
Discussion on SDR requirements for FR2 DL 256QAM |
Intel Corporation |
R4-2014676 |
On SDR requirements for FR2 DL 256QAM |
China Telecom |
R4-2015315 |
Views on 256QAM SDR requirements for FR2 |
NTT DOCOMO, INC. |
R4-2015598 |
CR on SDR requirements for DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2015599 |
Discussion on SDR requirements for NR DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2015600 |
Summary of simulation results for SDR requirements |
Huawei, HiSilicon |
R4-2016093 |
Discussion on FR2 DL 256QAM |
Ericsson |
R4-2017538 |
CR on SDR requirements for DL 256QAM for FR2 |
Huawei, HiSilicon |
7.10.1.3 |
CSI requirements [NR_DL256QAM_FR2-Perf] |
|
R4-2014677 |
On CQI reporting requirements for FR2 DL 256QAM |
China Telecom |
R4-2014678 |
Summary of CQI reporting simulation results for FR2 DL 256QAM (TDD) |
China Telecom |
R4-2015601 |
Discussion and simulation results on CQI requirements for NR DL 256QAM for FR2 |
Huawei, HiSilicon |
R4-2016092 |
Discussion on FR2 DL 256QAM |
Ericsson |
R4-2016094 |
Simulation results for FR2 256QAM UE CQI performance requirements |
Ericsson |
7.11.1 |
RF core requirements maintenance [NR_RF_FR1-Core ] |
|
R4-2016042 |
CR Correction to NS_27 and Band 10 protection 38101-1 Rel16 |
Skyworks Solutions Inc. |
R4-2016614 |
Email discussion summary for [97e][112] NR_RF_FR1_Part_1 |
Moderator (Huawei) |
R4-2016816 |
WF on DC location reporting for intra-band UL CA |
Huawei, HiSilicon |
R4-2016817 |
LS on DC location reporting for intra-band UL CA |
RAN4 |
R4-2016956 |
Email discussion summary for [97e][112] NR_RF_FR1_Part_1 |
Moderator (Huawei) |
7.11.1.1 |
Intra-band contiguous DL CA for FR1 [NR_RF_FR1-Core] |
|
R4-2014956 |
CR to TS 38.101-1 on operating bands for intra-band CA (Rel-16) |
ZTE Corporation |
7.11.1.2 |
Intra-band UL CA for FR1 power class 3 [NR_RF_FR1-Core] |
|
R4-2014171 |
CA_n7B AMPR REFSENS |
Qualcomm Incorporated |
R4-2014518 |
A-MPR definition for CA_n7B, CA_n48B, CA_n41B and CA_n41C |
Nokia |
R4-2014519 |
Simulation results for CA_7B A-MPR. |
Nokia |
R4-2014909 |
FR1 intra-band UL NCCA frequency separation and power class |
Apple Inc. |
R4-2016009 |
CA_n7B 50MHz Measurements for A-MPR and MSD Test Points |
Skyworks Solutions Inc. |
R4-2016513 |
CR for intra-band UL CA non-contiguous CA requirement |
Huawei, HiSilicon |
R4-2016515 |
on FR1 intra-band UL CA Pcmax |
Huawei, HiSilicon |
R4-2016814 |
A-MPR definition for CA_n7B, CA_n48B, CA_n41B and CA_n41C |
Nokia |
R4-2016815 |
CR for intra-band UL CA non-contiguous CA requirement |
Huawei, HiSilicon, Nokia |
R4-2017824 |
A-MPR definition for CA_n7B, CA_n48B, CA_n41B and CA_n41C |
Nokia |
7.11.1.3 |
DC location for intra-band UL CA [NR_RF_FR1-Core] |
|
R4-2014714 |
DC location future compatible proposal |
Qualcomm Incorporated |
R4-2014910 |
DC location for intra-band UL CA |
Apple Inc. |
R4-2015212 |
More on DC location reporting for Intra band UL CA |
Nokia, Nokia Shanghai Bell |
R4-2015565 |
Clarification of DC location for intra-band UL CA |
Intel Corporation |
R4-2015997 |
Future proof UE DC location signaling for intra-band UL CA |
Skyworks Solutions Inc. |
R4-2016514 |
on FR1 UL CA DC location |
Huawei, HiSilicon |
7.11.1.4 |
Switching period between case 1 and case 2 [NR_RF_FR1-Core] |
|
R4-2014464 |
DL interruption for band combinations supporting carrier switching |
CATT |
R4-2015195 |
CR to 38.101-1 Add requirement on the UL CA configurations with no DL interruption |
China Telecom |
R4-2015196 |
CR to 38.101-3: Add requirement on the inter-band EN-DC with no DL interruption |
China Telecom |
R4-2015975 |
Modification of Pcmax for UL CA with uplink Tx switching capability |
Ericsson |
R4-2016818 |
CR to 38.101-1 Add requirement on the UL CA configurations with no DL interruption |
China Telecom |
R4-2016819 |
CR to 38.101-3: Add requirement on the inter-band EN-DC with no DL interruption |
China Telecom |
7.11.2 |
RRM core requirements maintenance (38.133) [NR_RF_FR1-Core] |
|
R4-2014505 |
CR to TS 38.133: Add information on the inter-band EN-DC and UL CA configurations with no DL interruption |
China Telecom |
R4-2014506 |
CR to TS 36.133: Add information on the inter-band EN-DC configurations with no DL interruption |
China Telecom |
R4-2015488 |
Correction on DL interruption on Tx Switching between two uplink carriers |
Huawei, HiSilicon |
R4-2017016 |
Email discussion summary for [97e][217] NR_RF_FR1_RRM |
Moderator (Huawei) |
R4-2017287 |
Email discussion summary for [97e][217] NR_RF_FR1_RRM |
Moderator (Huawei) |
7.11.3 |
RRM perf. requirements (38.133) [NR_RF_FR1-Perf] |
|
R4-2014503 |
Discussion on test case for DL interruptions at UE switching between two uplink carriers |
China Telecom |
R4-2014504 |
Draft CR to TS 38.133: Test case for DL interruptions at UE switching between two uplink carriers in FDD+TDD inter-band CA case |
China Telecom |
R4-2017172 |
Big CR: Introduction of Rel-16 NR FR1 RF WI RRM performance requirements |
Huawei, HiSilicon |
R4-2017173 |
WF on test case for DL interruption due to Tx switching between two uplink carriers |
Huawei, HiSilicon |
R4-2017324 |
Draft CR to TS 38.133: Test case for DL interruptions at UE switching between two uplink carriers in FDD+TDD inter-band CA case |
China Telecom |
7.11.3.2 |
Test cases [NR_RF_FR1-Perf] |
|
R4-2014733 |
Discussion on test case on TX switching between two TDD uplink carriers |
CMCC |
R4-2014734 |
Draft CR to TS 38.133: Test case for DL interruptions at UE switching between two uplink carriers in TDD+TDD inter-band CA case |
CMCC |
R4-2015486 |
Discussion on test case on TX switching between two uplink carriers |
Huawei, HiSilicon |
R4-2015487 |
Test case for DL Interruptions at UE switching between LTE 1Tx carrier and NR 2Tx carrier in inter-band ENDC |
Huawei, HiSilicon |
R4-2017325 |
Draft CR to TS 38.133: Test case for DL interruptions at UE switching between two uplink carriers in TDD+TDD inter-band CA case |
CMCC |
R4-2017326 |
Test case for DL Interruptions at UE switching between LTE 1Tx carrier and NR 2Tx carrier in inter-band ENDC |
Huawei, HiSilicon |
R4-2017346 |
Draft CR to TS 38.133: Test case for DL interruptions at UE switching between two uplink carriers in TDD+TDD inter-band CA case |
CMCC |
7.12.1 |
RF core requirements maintenance [NR_RF_FR2_req_enh-Core] |
|
R4-2016615 |
Email discussion summary for [97e][113] NR_RF_FR2_req_enh_Part_4 |
Moderator (Nokia) |
R4-2016820 |
WF on Beam Correspondence based on configured DL RS (SSB or CSI-RS) |
Apple |
R4-2016824 |
WF on addition of new frequency separation classes |
Qualcomm |
R4-2016957 |
Email discussion summary for [97e][113] NR_RF_FR2_req_enh_Part_4 |
Moderator (Nokia) |
7.12.1.1 |
Beam Correspondence based on configured DL RS (SSB or CSI-RS) [NR_RF_FR2_req_enh-Core] |
|
R4-2014320 |
Enhanced beam correspondence test applicability rules in rel-16 |
LG Electronics France |
R4-2014512 |
REL16 eBC capability alingment with 38.306 |
Nokia, Nokia Shanghai Bell |
R4-2014584 |
On CSI-RS based beam correspondence |
Intel Corporation |
R4-2014722 |
Discussion on Rel-16 beam correspondence remaining issues |
Samsung |
R4-2014923 |
Remaining issues with beam correspondence enhancement |
Apple Inc. |
R4-2014924 |
CR to TR 38.831 on beam correspondence corrections |
Apple Inc. |
R4-2015344 |
Discussion on Rel-16 BC |
OPPO |
R4-2015808 |
Remaining issues in beam correspondence |
Sony, Ericsson |
R4-2016518 |
CR on beam correspondence side condition |
Huawei, HiSilicon |
R4-2016821 |
REL16 eBC capability alingment with 38.306 |
Nokia, Nokia Shanghai Bell |
R4-2016822 |
CR to TR 38.831 on beam correspondence corrections |
Apple Inc. |
R4-2016823 |
CR on beam correspondence side condition |
Huawei, HiSilicon |
7.12.1.2 |
Others [NR_RF_FR2_req_enh-Core] |
|
R4-2014290 |
Inter-band + intra-band CA FR2 frequency separation class |
Qualcomm Incorporated |
R4-2014581 |
CR to 38.101-2 (Rel-16) inter-band DL CA |
Intel Corporation |
R4-2014585 |
Rel-16 Inter-band DL CA requirements |
Intel Corporation |
R4-2014597 |
Clarification of EIS spherical coverage for inter-band CA |
Qualcomm Incorporated |
R4-2014932 |
CR for PSD imbalance for FR2 DL inter-band CA |
NTT DOCOMO INC. |
R4-2015088 |
CR to TR 38.831 to include DL CA agreement |
Nokia, Nokia Shanghai Bell |
R4-2015343 |
Discussion on Rel-16 FR2 inter-band DL CA |
OPPO |
R4-2016519 |
CR for inter-band NC DL CA Rrefsens |
Huawei, HiSilicon |
R4-2016825 |
CR to 38.101-2 (Rel-16) inter-band DL CA |
Intel Corporation |
R4-2016826 |
Clarification of EIS spherical coverage for inter-band CA |
Qualcomm Incorporated |
R4-2016827 |
CR to TR 38.831 to include DL CA agreement |
Nokia, Nokia Shanghai Bell |
R4-2016828 |
CR for inter-band NC DL CA Rrefsens |
Huawei, HiSilicon |
7.13 |
NR RRM requirement enhancement [NR_RRM_Enh-Core] |
|
R4-2017017 |
Email discussion summary for [97e][218] NR_RRM_Enh_RRM_1 |
Moderator (Intel Corporation) |
R4-2017018 |
Email discussion summary for [97e][219] NR_RRM_Enh_RRM_2 |
Moderator (ZTE Corporation) |
R4-2017019 |
Email discussion summary for [97e][220] NR_RRM_Enh_RRM_3 |
Moderator (Apple) |
R4-2017174 |
WF on R16 RRM enhancement part 1 |
Intel Corporation |
R4-2017180 |
WF on R16 RRM enhancement part 2 |
ZTE Corporation |
R4-2017201 |
WF on R16 RRM enhancement part 3 - FR2 inter-band CA RRM |
Huawei |
R4-2017202 |
WF on R16 RRM enhancement part 3 |
Apple |
R4-2017203 |
WF on R16 RRM enhancement part 3 - Inter-frequency measurement without MG |
CMCC |
R4-2017288 |
Email discussion summary for [97e][218] NR_RRM_Enh_RRM_1 |
Moderator (Intel Corporation) |
R4-2017289 |
Email discussion summary for [97e][219] NR_RRM_Enh_RRM_2 |
Moderator (ZTE Corporation) |
R4-2017290 |
Email discussion summary for [97e][220] NR_RRM_Enh_RRM_3 |
Moderator (Apple) |
R4-2017362 |
WF on R16 RRM enhancement part 1 |
Intel Corporation |
R4-2017363 |
WF on R16 RRM enhancement part 2 |
ZTE Corporation |
7.13.1.1 |
SRS carrier switching requirements [NR_RRM_Enh_Core] |
|
R4-2014646 |
38.133 CR on conditions for NR SRS carrier switching |
Qualcomm, Inc. |
R4-2015577 |
CR to 38.133: Correction to SRS carrier based switching requirements |
ZTE |
R4-2016421 |
Missing requirements for LTE SRS carrier-based switching |
Ericsson |
R4-2016422 |
Correction in NR SRS carrier-based switching requirements |
Ericsson |
R4-2017181 |
38.133 CR on conditions for NR SRS carrier switching |
Qualcomm, Inc. |
R4-2017182 |
CR to 38.133: Correction to SRS carrier based switching requirements |
ZTE |
7.13.1.2 |
CGI reading requirements with autonomous gap [NR_RRM_Enh_Core] |
|
R4-2015575 |
CR to 38.133: Correction to relaxed measurement requirements |
ZTE |
R4-2015576 |
CR to 36.133: Correction to NR CGI reading interruption requirements |
ZTE |
R4-2015774 |
CR on CGI reading requirements 38.133 |
Huawei, HiSilicon |
R4-2015775 |
CR on CGI reading requirements 36.133 |
Huawei, HiSilicon |
R4-2016379 |
Maintenance CR on NR CGI reading in 36.133 |
Nokia, Nokia Shanghai Bell |
R4-2017189 |
CR to 38.133: Correction to relaxed measurement requirements |
ZTE |
R4-2017190 |
CR to 36.133: Correction to NR CGI reading interruption requirements |
ZTE |
R4-2017191 |
CR on CGI reading requirements 38.133 |
Huawei, HiSilicon |
R4-2017192 |
CR on CGI reading requirements 36.133 |
Huawei, HiSilicon |
R4-2017193 |
Maintenance CR on NR CGI reading in 36.133 |
Nokia, Nokia Shanghai Bell |
7.13.1.3 |
BWP switching on multiple CCs [NR_RRM_Enh_Core] |
|
R4-2014570 |
Discussion of RRC based BWP switching on multiple CCs |
Intel Corporation |
R4-2014773 |
Remaining issues on multiple BWP switch |
MediaTek inc. |
R4-2014774 |
CR on multiple BWP switch in R16 |
MediaTek inc. |
R4-2014837 |
CR for simultaneous DCI based BWP switch delay on multiple CCs |
vivo |
R4-2015304 |
Discussion on cross carrier BWP switch delay requirements for single and multiple CC |
NEC |
R4-2015305 |
CR to TS 38.133 on DCI based BWP switch requirements for cross carrier scheduling |
NEC |
R4-2015505 |
CR on interruption due to active BWP switching on mulitple CCs |
Huawei, HiSilicon |
R4-2015506 |
Discussion on requirements maintenance for BWP switch on multiple CCs |
Huawei, HiSilicon |
R4-2016165 |
Analysis of RRC based non-simultaneous multiple CC BWP |
Ericsson |
R4-2016166 |
Correction to RRC based non-simultaneous multiple CC BWP |
Ericsson |
R4-2016427 |
On Active BWP switching under cross-carrier scheduling |
Ericsson |
R4-2016428 |
CR 38.133 Active BWP switching with cross-carrier scheduling |
Ericsson |
R4-2017175 |
CR on interruption due to active BWP switching on mulitple CCs |
Huawei, HiSilicon |
R4-2017176 |
Correction to RRC based non-simultaneous multiple CC BWP |
Ericsson |
R4-2017323 |
CR to TS 38.133 on DCI based BWP switch requirements for cross carrier scheduling |
NEC |
7.13.1.4 |
Spatial relation switch for uplink [NR_RRM_Enh_Core] |
|
R4-2014250 |
Requirements for UL spatial relation info switch |
Apple |
R4-2014771 |
Remaining issues on active spatial relation switch |
MediaTek inc. |
R4-2015308 |
Discussion on spatial relation switch for uplink |
NTT DOCOMO, INC. |
R4-2015498 |
Discussion on the remaining issues on spatial relation switch |
Huawei, HiSilicon |
R4-2015499 |
Correction on RRC based spatial relation switch delay |
Huawei, HiSilicon |
R4-2016026 |
CR 38.133 Corrections to MAC-CE and RRC-based spatial relation switching requirements |
Ericsson |
7.13.1.5 |
Inter-band CA requirement for FR2 UE measurement capability of independent Rx beam and/or common beam [NR_RRM_Enh_Core] |
|
R4-2014275 |
Draft CR on maintenance for inter-band FR2 CA RRM |
Apple |
R4-2014873 |
Discussion on Inter-band CA requirement for FR2 |
MediaTek inc. |
R4-2014874 |
Correction on unknown SCell activation in FR2. |
MediaTek inc. |
R4-2015309 |
Discussion on inter-band CA requirement for FR2 |
NTT DOCOMO, INC. |
R4-2015985 |
CR on measurement restrictions for FR2 inter-band CA |
Intel Corporation |
R4-2016576 |
BM resources for FR2 Inter-band IBM UEs |
Qualcomm Incorporated |
R4-2017204 |
Draft CR on maintenance for inter-band FR2 CA RRM |
Apple |
R4-2017205 |
Correction on unknown SCell activation in FR2. |
MediaTek inc. |
7.13.1.6 |
Other requirements maintenance [NR_RRM_Enh_Core] |
|
R4-2014277 |
Draft CR on UE behavior for UE specific CBW change |
Apple |
R4-2014364 |
CR on TS38.133 for inter-frequency measurement requirement without gap |
MediaTek inc. |
R4-2014772 |
Remaining Issues on multiple SCell Activation |
MediaTek inc. |
R4-2014861 |
Editorial CR for inter frequency measurements without measurement gaps (9.3.9) |
Apple |
R4-2015496 |
CR on inter-frequency measurement without gap |
Huawei, HiSilicon |
R4-2015578 |
CR to 38.133: Correction to mandatory gap pattern |
ZTE |
R4-2015579 |
CR to 36.133: Introduce requirements for mandatory gap pattern |
ZTE |
R4-2015771 |
Discussion on remaining issues in multiple SCell activation |
Huawei, HiSilicon |
R4-2015772 |
CR on SCell activation requirements |
Huawei, HiSilicon |
R4-2016019 |
CR 38.133 Removal of brackets for Multiple SCell activation |
Ericsson |
R4-2016574 |
Multi-SCell activation for FR1 intra-band contiguous CA |
Qualcomm Incorporated |
R4-2016583 |
CR to Multi-SCell activation for FR1 intra-band contiguous CA |
Qualcomm Incorporated |
R4-2017199 |
CR to 38.133: Correction to mandatory gap pattern |
ZTE |
R4-2017200 |
CR to 36.133: Introduce requirements for mandatory gap pattern |
ZTE |
R4-2017206 |
CR on SCell activation requirements |
Huawei, HiSilicon |
R4-2017207 |
CR to Multi-SCell activation for FR1 intra-band contiguous CA |
Qualcomm Incorporated |
R4-2017208 |
CR on inter-frequency measurement without gap |
Huawei, HiSilicon |
R4-2017209 |
Draft CR on UE behavior for UE specific CBW change |
Apple |
7.13.2.1 |
General [NR_RRM_Enh-Perf] |
|
R4-2014566 |
Work plan of Rel-16 NR RRM enhancements WI performance part |
Intel Corporation, ZTE Corporation, Apple |
R4-2016420 |
On test cases for SRS carrier-based switching in NR |
Ericsson |
R4-2017222 |
Work plan of Rel-16 NR RRM enhancements WI performance part |
Intel Corporation, ZTE Corporation, Apple |
R4-2017386 |
Draft Big CR: Introduction of Rel-16 NR RRM enhancements WI performance requirements and test cases |
Intel Corporation, ZTE Corporation, Apple |
7.13.2.2.1 |
SRS carrier switching requirements [NR_RRM_Enh-Perf] |
|
R4-2014227 |
E-UTRAN – NR FR2 interruptions at NR SRS carrier based switching (A.5.5.2.X) |
Apple |
R4-2014789 |
CR to TS 38.133 TC for E-UTRAN |
OPPO |
R4-2015495 |
TC for E-UTRAN |
Huawei, HiSilicon |
R4-2015581 |
Test case list for SRS carrier based switching |
ZTE |
R4-2015584 |
Draft CR on test case for SA interruptions at NR SRS carrier based switching |
ZTE |
R4-2016052 |
38133 CR for Test case of E-UTRAN NR FR1 interruptions at NR SRS carrier switching |
Nokia, Nokia Shanghai Bell |
R4-2016423 |
On TC2 configuration (SA interruptions at NR SRS carrier-based switching) |
Ericsson |
R4-2017183 |
E-UTRAN – NR FR2 interruptions at NR SRS carrier based switching (A.5.5.2.X) |
Apple |
R4-2017184 |
CR to TS 38.133 TC for E-UTRAN |
OPPO |
R4-2017185 |
TC for E-UTRAN |
Huawei, HiSilicon |
R4-2017186 |
Draft CR on test case for SA interruptions at NR SRS carrier based switching |
ZTE |
R4-2017187 |
38133 CR for Test case of E-UTRAN NR FR1 interruptions at NR SRS carrier switching |
Nokia, Nokia Shanghai Bell |
R4-2017188 |
On TC2 configuration (SA interruptions at NR SRS carrier-based switching) |
Ericsson |
R4-2017364 |
E-UTRAN – NR FR2 interruptions at NR SRS carrier based switching (A.5.5.2.X) |
Apple |
R4-2017365 |
Draft CR on test case for SA interruptions at NR SRS carrier based switching |
ZTE |
R4-2017366 |
38133 CR for Test case of E-UTRAN NR FR1 interruptions at NR SRS carrier switching |
Nokia, Nokia Shanghai Bell |
7.13.2.2.2 |
Multiple Scell activation/deactivation [NR_RRM_Enh-Perf] |
|
R4-2014276 |
Test case of SCell activation and deactivation of multiple unknown SCells in FR1 with single activation/deactivation command |
Apple |
R4-2014777 |
DraftCR on multiple SCell activation with FR1+FR2 unknown cells in NR-DC Test Case |
MediaTek inc. |
R4-2015580 |
Test case list for NR CGI reading with autonomous gaps |
ZTE |
R4-2015583 |
Draft CR on test case for SA intra-frequency CGI identification of NR neighbor cell in FR1 |
ZTE |
R4-2015773 |
draftCR to introduce multiple SCell activation TC2 |
Huawei, HiSilicon |
R4-2017196 |
Draft CR on test case for SA intra-frequency CGI identification of NR neighbor cell in FR1 |
ZTE |
R4-2017210 |
Test case of SCell activation and deactivation of multiple unknown SCells in FR1 with single activation/deactivation command |
Apple |
R4-2017211 |
DraftCR on multiple SCell activation with FR1+FR2 unknown cells in NR-DC Test Case |
MediaTek inc. |
R4-2017212 |
draftCR to introduce multiple SCell activation TC2 |
Huawei, HiSilicon |
7.13.2.2.3 |
CGI reading requirements with autonomous gap [NR_RRM_Enh-Perf] |
|
R4-2014642 |
CGI reading test scope and requirement discussion |
Qualcomm, Inc. |
R4-2014776 |
DraftCR on SA CGI identification of E-UTRA neighbor cell Test Case |
MediaTek inc. |
R4-2015171 |
Test case list and configurations for CGI reading |
Ericsson |
R4-2015172 |
CR to introduce interfrequency FR2 CGI reading test for SA NR (TC2) |
Ericsson |
R4-2015776 |
draftCR on TC for EN-DC inter-frequency CGI identification of NR neighbor cell in FR2 |
Huawei, HiSilicon |
R4-2016380 |
Test cases for EN-DC intra-frequency CGI identification of NR neighbour cell in FR1 |
Nokia, Nokia Shanghai Bell |
R4-2017194 |
DraftCR on SA CGI identification of E-UTRA neighbor cell Test Case |
MediaTek inc. |
R4-2017195 |
CR to introduce interfrequency FR2 CGI reading test for SA NR (TC2) |
Ericsson |
R4-2017197 |
draftCR on TC for EN-DC inter-frequency CGI identification of NR neighbor cell in FR2 |
Huawei, HiSilicon |
R4-2017198 |
Test cases for EN-DC intra-frequency CGI identification of NR neighbour cell in FR1 |
Nokia, Nokia Shanghai Bell |
7.13.2.2.4 |
BWP switching on multiple CCs [NR_RRM_Enh-Perf] |
|
R4-2014251 |
Discussion on testcases for BWP switching on multiple CCs |
Apple |
R4-2014567 |
Discussion on test cases for BWP switching on multiple CCs |
Intel Corporation |
R4-2014568 |
CR on simultaneous DCI-based and Timer-based Active BWP Switch on multiple CCs on FR1 in EN-DC (section 4.5.6.3) |
Intel Corporation |
R4-2014778 |
Discussion on multiple BWP switch test case |
MediaTek inc. |
R4-2014838 |
CR for test cases for simultaneously DCI/timer based bwp switch over mulitple CCs |
vivo |
R4-2014839 |
Discussion on test cases for BWP switch on multiple CCs |
vivo |
R4-2015507 |
Discussion on performance requirements for BWP switch on multiple CCs |
Huawei, HiSilicon |
R4-2016167 |
Test cases for BWP switching on multiple CCs |
Ericsson |
R4-2016381 |
discussion on the test cases for BWP switch on multiple CCs |
Nokia, Nokia Shanghai Bell |
R4-2016572 |
Performance requirements for BWP switching on multiple CCs |
Qualcomm Incorporated |
7.13.2.2.5 |
Inter-frequency measurement requirement without MG [NR_RRM_Enh-Perf] |
|
R4-2014226 |
Test case for inter-frequency measurement without gap: SA event triggered reporting tests for FR1 when DRX is used (A.6.6.2.X) |
Apple |
R4-2014365 |
CR on TS38.133 SA event triggered reporting tests for FR2 without gap when DRX is used (A.7.6.2.X) |
MediaTek inc. |
R4-2014645 |
Inter-f without MG test scope and configuration discussion |
Qualcomm, Inc. |
R4-2014731 |
Discussion on test case on inter-frequency measurement without MG |
CMCC |
R4-2014732 |
Draft CR to TS 38.133: SA event triggered reporting tests for FR1 without gap when DRX is not used (A.6.6.2.X) |
CMCC |
R4-2015497 |
Test case for Inter-frequency measurements: SA event triggered reporting tests for FR2 without gap when DRX is not used |
Huawei, HiSilicon |
R4-2017213 |
Test case for inter-frequency measurement without gap: SA event triggered reporting tests for FR1 when DRX is used (A.6.6.2.X) |
Apple |
R4-2017214 |
CR on TS38.133 SA event triggered reporting tests for FR2 without gap when DRX is used (A.7.6.2.X) |
MediaTek inc. |
R4-2017215 |
Draft CR to TS 38.133: SA event triggered reporting tests for FR1 without gap when DRX is not used (A.6.6.2.X) |
CMCC |
R4-2017216 |
Test case for Inter-frequency measurements: SA event triggered reporting tests for FR2 without gap when DRX is not used |
Huawei, HiSilicon |
R4-2017369 |
CR on TS38.133 SA event triggered reporting tests for FR2 without gap when DRX is used (A.7.6.2.X) |
MediaTek inc. |
R4-2017387 |
CR on TS38.133 SA event triggered reporting tests for FR2 without gap when DRX is used (A.7.6.2.X) |
MediaTek inc. |
7.13.2.2.6 |
Mandatory MG patterns [NR_RRM_Enh-Perf] |
|
R4-2014228 |
Testing applicability for new mandatory gap patterns |
Apple |
R4-2014643 |
Mandatory gap pattern test scope and applicability rule discussion |
Qualcomm, Inc. |
R4-2014644 |
Mandatory gap pattern test |
Qualcomm, Inc. |
R4-2015174 |
Test case list for mandatory measurement gap |
Ericsson |
R4-2015175 |
Test cases for mandatory measurement gap |
Ericsson |
R4-2015582 |
Test case list for mandatory gap pattern |
ZTE |
R4-2015585 |
Draft CR on test case for SA event triggered reporting tests with additional mandatory gap pattern |
ZTE |
R4-2017339 |
Test cases for mandatory measurement gap |
Ericsson |
R4-2017340 |
Draft CR on test case for SA event triggered reporting tests with additional mandatory gap pattern |
ZTE |
7.13.2.2.7 |
UE-specific CBW change [NR_RRM_Enh-Perf] |
|
R4-2014278 |
Test case list for UE specific CBW change |
Apple |
R4-2014279 |
Test case of UE specific CBW change on FR1 NR PSCell with non-DRX in synchronous EN-DC |
Apple |
R4-2015302 |
Draft CR on TC for UE specific CBW change on FR2 NR PCell in NR SA |
NEC |
R4-2015777 |
draftCR on TC for UE specific CBW change on FR2 NR PSCell in EN-DC |
Huawei, HiSilicon |
R4-2016168 |
Analysis of TC3: UE specific CBW change on FR1 NR PCell in NR SA |
Ericsson |
R4-2016169 |
TC3: UE specific CBW change on FR1 NR PCell in NR SA (A.6.5.7) |
Ericsson |
R4-2017217 |
Test case of UE specific CBW change on FR1 NR PSCell with non-DRX in synchronous EN-DC |
Apple |
R4-2017218 |
Draft CR on TC for UE specific CBW change on FR2 NR PCell in NR SA |
NEC |
R4-2017219 |
draftCR on TC for UE specific CBW change on FR2 NR PSCell in EN-DC |
Huawei, HiSilicon |
R4-2017220 |
TC3: UE specific CBW change on FR1 NR PCell in NR SA (A.6.5.7) |
Ericsson |
7.13.2.2.8 |
Spatial relation switch for uplink [NR_RRM_Enh-Perf] |
|
R4-2014569 |
Discussion on test cases for UL spatial relation switch |
Intel Corporation |
R4-2014775 |
DraftCR on spatial relation switch test case |
MediaTek inc. |
R4-2015500 |
TC for RRC based spatial relation switch associated with a known DL-RS |
Huawei, HiSilicon |
R4-2015885 |
RRC based spatial relation switch associated with a known DL-RS in SA |
Nokia, Nokia Shanghai Bell |
R4-2016014 |
On TC3 MAC-CE based spatial relation info switching |
Ericsson |
R4-2016015 |
CR 38.133 TC3 MAC-CE based spatial relation info switching |
Ericsson |
R4-2017177 |
DraftCR on spatial relation switch test case |
MediaTek inc. |
R4-2017178 |
TC for RRC based spatial relation switch associated with a known DL-RS |
Huawei, HiSilicon |
R4-2017179 |
CR 38.133 TC3 MAC-CE based spatial relation info switching |
Ericsson |
7.13.2.2.9 |
Inter-band CA requirement for FR2 UE measurement capability of independent Rx beam [NR_RRM_Enh-Perf] |
|
R4-2015173 |
Test case list for FR2 inter-band carrier aggregation |
Ericsson |
R4-2015475 |
Discussion on RRM test cases for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2015476 |
DraftCR on SCell activation and deactication delay test for FR2 inter-band CA |
Huawei, HiSilicon |
R4-2016577 |
Performance requirements for FR2 Inter-band IBM UEs |
Qualcomm Incorporated |
R4-2017221 |
DraftCR on SCell activation and deactication delay test for FR2 inter-band CA |
Huawei, HiSilicon |
7.14 |
NR RRM requirements for CSI-RS based L3 measurement [NR_CSIRS_L3meas] |
|
R4-2017020 |
Email discussion summary for [97e][221] NR_CSIRS_L3meas_RRM_1 |
Moderator (CATT) |
R4-2017021 |
Email discussion summary for [97e][222] NR_CSIRS_L3meas_RRM_2 |
Moderator (OPPO) |
R4-2017033 |
Email discussion summary for [97e][222] NR_CSIRS_L3meas_RRM_2 |
Moderator (OPPO) |
R4-2017291 |
Email discussion summary for [97e][221] NR_CSIRS_L3meas_RRM_1 |
Moderator (CATT) |
R4-2017292 |
Email discussion summary for [97e][222] NR_CSIRS_L3meas_RRM_2 |
Moderator (OPPO) |
7.14.1 |
RRM core requirements maintenance (38.133) [NR_CSIRS_L3meas-Core] |
|
R4-2014188 |
CR on scheduling restriction for CSI-RS based intra-frequency measurement |
Qualcomm CDMA Technologies |
R4-2014235 |
CR on CSSF with both CSI-RS and SSB |
Apple |
R4-2014236 |
On remaining core issues of CSI-RS for L3 measurements |
Apple |
R4-2014314 |
Discussions on the remaining issues for CSI-RS L3 core requirements |
Qualcomm CDMA Technologies |
R4-2014413 |
CR for TS36.133, Adding requirements for CSI-RS based L3 measurement |
CATT |
R4-2014429 |
CR on abbreviations about CSI-RS based measurement in 38.133. |
CATT |
R4-2014430 |
CR on CSI-RS based intra-frequency measurement |
CATT |
R4-2014431 |
CR on CSI-RS based inter-frequency measurement. |
CATT |
R4-2014432 |
CR on scheduling restriction for CSI-RS based intra-frequency measurement. |
CATT |
R4-2014433 |
CR on CSI-RS configuration for mobility |
CATT |
R4-2014434 |
CR on conditions for NR CSI-RS based L3 measurement |
CATT |
R4-2014530 |
Discussion on remaining issues for R16 CSI-RS based L3 measurements |
vivo |
R4-2014531 |
CR on R16 CSI-RS based L3 measurements |
vivo |
R4-2014622 |
On remaining issues for CSI-RS based L3 measurement |
MediaTek inc. |
R4-2014623 |
Introduction of CSSF requirements for CSI-RS based L3 measurement |
MediaTek inc., CATT |
R4-2014660 |
Maintenance on CSI-RS based L3 requirements |
Xiaomi |
R4-2014824 |
Discussion on remaining issues about CSI-RS based L3 measurement requirement |
NTT DOCOMO, INC. |
R4-2015489 |
Discussion on remaining issues for CSI-RS based L3 measurement |
Huawei, HiSilicon |
R4-2015490 |
CR on CSI-RS based intra-frequency measurement requirements |
Huawei, HiSilicon |
R4-2015491 |
CR on CSSF definition for CSI-RS based measurement |
Huawei, HiSilicon |
R4-2015782 |
CR on CSI-RS capability requirements and time restriction |
Huawei, HiSilicon |
R4-2016043 |
CSI-RS based intra-frequency measurement requirements |
Nokia, Nokia Shanghai Bell |
R4-2016044 |
38.133 CR on CSI-RS based intra-frequency measurement requirements |
Nokia, Nokia Shanghai Bell |
R4-2016045 |
38.133 CR on scheduling restrictions for CSI-RS based intra-frequency measurement |
Nokia, Nokia Shanghai Bell |
R4-2017223 |
WF on remaining issues on CSI-RS based L3 measurement requirements (core part) |
Apple |
R4-2017225 |
CR for TS36.133, Adding requirements for CSI-RS based L3 measurement |
CATT |
R4-2017226 |
CR on abbreviations about CSI-RS based measurement in 38.133. |
CATT |
R4-2017227 |
CR on R16 CSI-RS based L3 measurements |
vivo |
R4-2017228 |
CR on CSI-RS based intra-frequency measurement requirements |
Huawei, HiSilicon |
R4-2017316 |
CR on scheduling restriction for CSI-RS based intra-frequency measurement |
Qualcomm CDMA Technologies |
R4-2017317 |
CR on CSSF with both CSI-RS and SSB |
Apple |
R4-2017318 |
CR on conditions for NR CSI-RS based L3 measurement |
CATT |
R4-2017349 |
CR on scheduling restriction for CSI-RS based intra-frequency measurement |
Qualcomm CDMA Technologies |
7.14.2 |
RRM perf. requirements (38.133) [NR_CSIRS_L3meas-Perf] |
|
R4-2014666 |
RRM test cases for CSI-RS L3 measurement performance |
Xiaomi |
R4-2015213 |
CR on introduce the gain to CSI-RSRP measurements point in FR1 and FR2 |
Xiaomi |
R4-2017224 |
WF on performance requirements of CSI-RS based L3 measurement |
CATT |
R4-2017314 |
RRM test cases for CSI-RS L3 measurement performance |
Xiaomi |
R4-2017315 |
CR on introduce the gain to CSI-RSRP measurements point in FR1 and FR2 |
Xiaomi |
R4-2017367 |
WF on performance requirements of CSI-RS based L3 measurement |
CATT |
R4-2017388 |
Draft Big CR: Introduction of Rel-16 CSI-RS based L3 measurement RRM performance requirements |
CATT |
R4-2017389 |
Draft Big CR: Introduction of Rel-16 CSI-RS based L3 measurement RRM test cases |
OPPO |
7.14.2.1 |
General [NR_CSIRS_L3meas-Perf] |
|
R4-2014288 |
CR on introducing CSI-RS configurations for RRM |
Qualcomm CDMA Technologies |
R4-2014435 |
Work plan for CSI-RS based L3 measurements |
CATT |
R4-2014436 |
Updated link-level simulation assumptions for CSI-RS based L3 measurements |
CATT |
R4-2014659 |
Discussion on performance requirements for CSI-RS L3 measurements |
Xiaomi |
R4-2014664 |
CR on side conditions for CSI-RS based intra-frequency and inter-frequency measurements |
Xiaomi |
R4-2014790 |
Discussion on accuracy requirements for CSI-RS L3 measurements |
OPPO |
R4-2016046 |
Discussion on the performance of CSI-RS based intra-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2017229 |
Work plan for CSI-RS based L3 measurements |
CATT |
R4-2017230 |
Updated link-level simulation assumptions for CSI-RS based L3 measurements |
CATT |
R4-2017337 |
CR on introducing CSI-RS configurations for RRM |
Qualcomm CDMA Technologies |
7.14.2.1.1 |
CSI-RSRP requirements [NR_CSIRS_L3meas -Perf] |
|
R4-2014354 |
Simulation results on CSI-RS based L3 measurements for RSRP |
Qualcomm CDMA Technologies |
R4-2014437 |
Simulation results for CSI-RSRP measurement |
CATT |
R4-2014439 |
Discussion on performance requirement for CSI-RSRP |
CATT |
R4-2014441 |
CR on performance requirement for CSI-RSRP L3 measurement |
CATT |
R4-2014624 |
CSI-RSRP measurement accuracy requirements |
MediaTek inc. |
R4-2014661 |
CR on CSI-RSRP performance requirements for CSI-RS based measurements |
Xiaomi |
R4-2014703 |
Simulation results for CSI-RSRP measurement |
CMCC |
R4-2014791 |
CR to TS 38.133 on CSI-RSRP measurement accuracy(section 10.1) |
OPPO |
R4-2015783 |
Discussion on CSI-RSRP accuracy and report mapping |
Huawei, HiSilicon |
R4-2015784 |
CR to introduce CSI-RSRP accuracy requirements and report mapping |
Huawei, HiSilicon |
R4-2016047 |
38.133 CR on the intra-frequency CSI-RSRP accuracy requirements |
Nokia, Nokia Shanghai Bell |
R4-2016048 |
38.133 CR on the conditions for NR intra-frequency CSI-RS based measurements |
Nokia, Nokia Shanghai Bell |
R4-2016049 |
Simulation results for CSI-RS based measurements |
Nokia, Nokia Shanghai Bell |
R4-2017319 |
38.133 CR on the intra-frequency CSI-RSRP accuracy requirements |
Nokia, Nokia Shanghai Bell |
7.14.2.1.2 |
CSI-RSRQ requirements [NR_CSIRS_L3meas -Perf] |
|
R4-2014438 |
Simulation results for CSI-RSRQ measurement |
CATT |
R4-2014440 |
Discussion on performance requirement for CSI-RSRQ |
CATT |
R4-2014442 |
CR on performance requirement for CSI-RSRQ L3 measurement |
CATT |
R4-2014662 |
CR on CSI-RSRQ performance requirements for CSI-RS based L3 measurements |
Xiaomi |
R4-2014792 |
CR to TS 38.133 on CSI-RSRQ measurement accuracy(section 10.1) |
OPPO |
R4-2015785 |
Discussion on CSI-RSRQ accuracy requirements and report mapping |
Huawei, HiSilicon |
R4-2015786 |
CR to introduce CSI-RSRQ accuracy requirements and report mapping |
Huawei, HiSilicon |
R4-2017320 |
CR on performance requirement for CSI-RSRQ L3 measurement |
CATT |
R4-2017348 |
CR on performance requirement for CSI-RSRQ L3 measurement |
CATT |
7.14.2.1.3 |
CSI-SINR requirements [NR_CSIRS_L3meas -Perf] |
|
R4-2014443 |
CR on performance requirement for CSI-SINR L3 measurement |
CATT |
R4-2014625 |
CSI-SINR measurement accuracy requirements |
MediaTek inc. |
R4-2014663 |
CR on CSI-SINR performance requirements for CSI-RS based L3 measurements |
Xiaomi |
R4-2015787 |
Discussion on CSI-SINR accuracy requirements and report mapping |
Huawei, HiSilicon |
R4-2015788 |
CR to introduce CSI-SINR accuracy requirements and report mapping |
Huawei, HiSilicon |
R4-2017321 |
CR to introduce CSI-SINR accuracy requirements and report mapping |
Huawei, HiSilicon |
7.14.2.2 |
Test cases [NR_CSIRS_L3meas-Perf] |
|
R4-2014189 |
Draft test case CR on EN-DC event triggered reporting tests without gap for NR neighbor cell in FR2 |
Qualcomm CDMA Technologies |
R4-2014287 |
Draft test case CR on EN-DC CSI-RSRP measurement accuracy for NR neighbor cell in FR2 |
Qualcomm CDMA Technologies |
R4-2014444 |
Test case for CSI-RS based L3 measurement |
CATT |
R4-2014532 |
CR on test cases for EN-DC CSI-SINR measurement accuracy |
vivo |
R4-2014626 |
Introduction of test case for CSI-SINR in SA FR2 |
MediaTek inc. |
R4-2014665 |
RRM test cases for CSI-RS L3 intra-frequency and inter-frequency measurements |
Xiaomi |
R4-2014699 |
Discussion on test cases for CSI-RS based RRM measurement |
CMCC |
R4-2014793 |
CR to TS 38.133: EN-DC event triggered reporting tests for NR neighbour cell in FR2 (PScell in FR1) for CSI-RS L3 inter-frequency measurements(A.5.6.x) |
OPPO |
R4-2014794 |
CR to TS 38.133: TC for EN-DC CSI-RSRQ measurement accuracy for all NR cells in FR1(A.4.7.x) |
OPPO |
R4-2014795 |
CR to TS 38.133: TC for EN-DC CSI-RSRQ measurement accuracy for all NR cells in FR2(A.5.7.x) |
OPPO |
R4-2015586 |
Draft CR on test case for SA CSI-RS based measurement in FR2 and CSI-RSRQ accuracy in FR2 |
ZTE |
R4-2015789 |
CR to introduce TC for CSI-SINR measurement accuracy for FR1 SA and FR2 EN-DC |
Huawei, HiSilicon |
R4-2016050 |
38.133 CR on the test case of EN-DC event triggered reporting for intra-frequency CSI-RS based measurements in FR1 |
Nokia, Nokia Shanghai Bell |
R4-2016051 |
38.133 CR on the test cases of EN-DC measurement accuracy in FR1 for CSI-RS based intra-frequency and inter-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2017231 |
Draft test case CR on EN-DC event triggered reporting tests without gap for NR neighbor cell in FR2 |
Qualcomm CDMA Technologies |
R4-2017232 |
Draft test case CR on EN-DC CSI-RSRP measurement accuracy for NR neighbor cell in FR2 |
Qualcomm CDMA Technologies |
R4-2017233 |
Test case for CSI-RS based L3 measurement |
CATT |
R4-2017234 |
RRM test cases for CSI-RS L3 intra-frequency and inter-frequency measurements |
Xiaomi |
R4-2017235 |
Introduction of test case for CSI-SINR in SA FR2 |
MediaTek inc. |
R4-2017236 |
CR to TS 38.133: EN-DC event triggered reporting tests for NR neighbour cell in FR2 (PScell in FR1) for CSI-RS L3 inter-frequency measurements(A.5.6.x) |
OPPO |
R4-2017237 |
Draft CR on test case for SA CSI-RS based measurement in FR2 and CSI-RSRQ accuracy in FR2 |
ZTE |
R4-2017238 |
38.133 CR on the test case of EN-DC event triggered reporting for intra-frequency CSI-RS based measurements in FR1 |
Nokia, Nokia Shanghai Bell |
R4-2017239 |
38.133 CR on the test cases of EN-DC measurement accuracy in FR1 for CSI-RS based intra-frequency and inter-frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2017310 |
CR to TS 38.133: TC for EN-DC CSI-RSRQ measurement accuracy for all NR cells in FR1(A.4.7.x) |
OPPO |
R4-2017311 |
CR to TS 38.133: TC for EN-DC CSI-RSRQ measurement accuracy for all NR cells in FR2(A.5.7.x) |
OPPO |
R4-2017312 |
CR on test cases for EN-DC CSI-SINR measurement accuracy |
vivo |
R4-2017313 |
CR to introduce TC for CSI-SINR measurement accuracy for FR1 SA and FR2 EN-DC |
Huawei, HiSilicon |
R4-2017341 |
CR to TS 38.133: EN-DC event triggered reporting tests for NR neighbour cell in FR2 (PScell in FR2) for CSI-RS L3 inter-frequency measurements(A.5.6.x) |
OPPO |
7.15.1 |
RRM core requirements maintenance (38.133) [NR_HST-Core] |
|
R4-2014691 |
38.133 CR on CSSFintra for measurement period for intra-frequency measurements in connected mode for Rel-16 NR HST |
CMCC |
R4-2014964 |
CR on IDLE state cell re-selection requirements for HST in 38.133 |
vivo,Huawei, HiSilicon |
R4-2014965 |
CR on IDLE state cell-reselection requirements for HST in 36.133 |
vivo,Huawei, HiSilicon |
R4-2014981 |
CR on IDLE state cell re-selection requirements for HST in 36.133 |
vivo, Huawei, HiSilicon |
R4-2015156 |
Correction to high speed idle mode core requirement |
Ericsson |
R4-2015492 |
Correction on SSB based L1-RSRP Reporting for HST |
Huawei, HiSilicon |
R4-2015804 |
Correction of CR0972 implementation |
ETSI MCC |
R4-2016207 |
CR to TS 38.133: Corrections to Tables 9.5.4.1-1 and 9.5.4.2-1. |
Nokia, Nokia Shanghai Bell |
R4-2017022 |
Email discussion summary for [97e][223] NR_HST_RRM |
Moderator (CMCC) |
R4-2017240 |
CR on IDLE state cell re-selection requirements for HST in 38.133 |
vivo,Huawei, HiSilicon |
R4-2017241 |
CR on IDLE state cell re-selection requirements for HST in 36.133 |
vivo, Huawei, HiSilicon |
R4-2017242 |
38.133 CR on CSSFintra for measurement period for intra-frequency measurements in connected mode for Rel-16 NR HST |
CMCC |
R4-2017293 |
Email discussion summary for [97e][223] NR_HST_RRM |
Moderator (CMCC) |
7.15.2 |
RRM perf. requirements (38.133) [NR_HST-Perf] |
|
R4-2017252 |
Big CR: NR HST RRM performance requirements |
CMCC |
7.15.2.1 |
General [NR_HST-Perf] |
|
R4-2014220 |
On HST intra-frequency measurement requirements |
Apple |
R4-2014221 |
CR for HST intra-frequency measurement requirements |
Apple |
R4-2014695 |
CR on release independent for Rel.16 NR HST RRM requirements |
CMCC |
R4-2014697 |
CR on release independent for Rel.16 NR HST RRM requirements |
CMCC |
R4-2015494 |
Accuracy requirements for NR high speed |
Huawei, HiSilicon |
R4-2017243 |
CR on release independent for Rel.16 NR HST RRM requirements |
CMCC |
R4-2017244 |
CR on release independent for Rel.16 NR HST RRM requirements |
CMCC |
R4-2017245 |
Accuracy requirements for NR high speed |
Huawei, HiSilicon |
7.15.2.2 |
Test cases [NR_HST-Perf] |
|
R4-2014533 |
CR on test case for EUTRAN-NR cell re-selection in HST |
vivo |
R4-2014630 |
NR HST test case discussion |
Qualcomm, Inc. |
R4-2014631 |
CR-NR HST RRM test cases |
Qualcomm, Inc. |
R4-2014692 |
Draft CR on NR-NR intra-frequency reselection for FR1 for high speed scenario |
CMCC |
R4-2015147 |
Test cases for NR -NR cell identification in connected mode for high speed |
Ericsson |
R4-2015493 |
Test cases for inter-RAT cell identification in connected mode for HST |
Huawei, HiSilicon |
R4-2016215 |
CR to TS 38.133: Test cases for L1-RSRP measurement for beam reporting for NR HST |
Nokia, Nokia Shanghai Bell |
R4-2017246 |
CR on test case for EUTRAN-NR cell re-selection in HST |
vivo |
R4-2017247 |
CR-NR HST RRM test cases |
Qualcomm, Inc. |
R4-2017248 |
Draft CR on NR-NR intra-frequency reselection for FR1 for high speed scenario |
CMCC |
R4-2017249 |
Test cases for NR -NR cell identification in connected mode for high speed |
Ericsson |
R4-2017250 |
Test cases for inter-RAT cell identification in connected mode for HST |
Huawei, HiSilicon |
R4-2017251 |
CR to TS 38.133: Test cases for L1-RSRP measurement for beam reporting for NR HST |
Nokia, Nokia Shanghai Bell |
7.15.3.1 |
UE demodulation and CSI requirements [NR_HST-Perf] |
|
R4-2014633 |
View on NR HST demod |
Qualcomm, Inc. |
R4-2015602 |
Summary of ideal and impairment results for NR HST demodulation requirements |
Huawei, HiSilicon |
R4-2017424 |
Email discussion summary for [97e][326] NR_HST_Demod_UE |
Moderator (CMCC) |
R4-2017460 |
Email discussion summary for [97e][326] NR_HST_Demod_UE |
Moderator (CMCC) |
R4-2017549 |
WF on NR HST UE demodulation |
CMCC |
R4-2017624 |
Email discussion summary for [97e][326] NR_HST_Demod_UE |
Moderator (CMCC) |
R4-2017647 |
Summary of ideal and impairment results for NR HST demodulation requirements |
Huawei, HiSilicon |
7.15.3.1.1 |
Requirements for DPS transmission scheme(s) [NR_HST-Perf] |
|
R4-2014216 |
Discussion on DPS transmission scheme in HST |
Apple |
R4-2014553 |
Views on UE demodulation requirements for DPS transmission scheme for NR HST |
Intel Corporation |
R4-2014563 |
CR to TS 38.101-4: Propagation conditions for HST scenarios |
Intel Corporation |
R4-2014701 |
Further discussion on DPS for NR HST |
CMCC |
R4-2014704 |
Simulation results for DPS transmission scheme |
CMCC |
R4-2015020 |
UE demodulation requirements for DPS transmission scheme |
ZTE Corporation |
R4-2015603 |
CR on HST DPS requirements |
Huawei, HiSilicon |
R4-2015604 |
Discussion on UE performance requirements for DPS transmission scheme |
Huawei, HiSilicon |
R4-2015605 |
Simulation results on UE performance requirements for DPS 1a transmission scheme |
Huawei, HiSilicon |
R4-2015812 |
PDSCH demodulation requirements for HST-DPS |
Ericsson |
R4-2017539 |
CR to TS 38.101-4: Propagation conditions for HST scenarios |
Intel Corporation |
R4-2017540 |
CR on HST DPS requirements |
Huawei, HiSilicon |
7.15.3.1.2 |
Requirements for HST-SFN [NR_HST-Perf] |
|
R4-2014562 |
CR to TS 38.101-4: HST-SFN FDD performance requirements |
Intel Corporation |
R4-2014690 |
CR on HST-SFN requirements for TDD |
CMCC |
R4-2014696 |
CR on release independent for Rel.16 NR HST UE demodulation requirements |
CMCC |
R4-2014698 |
CR on release independent for Rel.16 NR HST UE demodulation requirements |
CMCC |
R4-2015813 |
Simulation results of PDSCH with HST-SFN |
Ericsson |
R4-2017541 |
CR on HST-SFN requirements for TDD |
CMCC |
R4-2017542 |
CR to TS 38.101-4: HST-SFN FDD performance requirements |
Intel Corporation |
R4-2017543 |
CR on release independent for Rel.16 NR HST UE demodulation requirements |
CMCC |
R4-2017544 |
CR on release independent for Rel.16 NR HST UE demodulation requirements |
CMCC |
7.15.3.1.3 |
Requirements for HST single tap [NR_HST-Perf] |
|
R4-2015606 |
CR on HST single-tap and HST multi-path fading requirements |
Huawei, HiSilicon |
R4-2016108 |
CR to TS38.101-4: Addition of Rel-16 HST FRCs |
Ericsson |
R4-2016500 |
CR on FDD HST Single-Tap and Multipath Fading Requirements |
Qualcomm Incorporated |
R4-2017545 |
CR on HST single-tap and HST multi-path fading requirements |
Huawei, HiSilicon |
R4-2017546 |
CR to TS38.101-4: Addition of Rel-16 HST FRCs |
Ericsson |
R4-2017547 |
CR on FDD HST Single-Tap and Multipath Fading Requirements |
Qualcomm Incorporated |
R4-2017682 |
CR on FDD HST Single-Tap and Multipath Fading Requirements |
Qualcomm Incorporated |
7.15.3.1.5 |
Applicability rule [NR_HST-Perf] |
|
R4-2014217 |
Discussion on applicability rule for HST test |
Apple |
R4-2014700 |
Discussion on applicability rule for UE demodulation requirements for NR HST |
CMCC |
R4-2015313 |
Views on HST applicability rules |
NTT DOCOMO, INC. |
R4-2015607 |
CR on applicability rules for HST scenarios |
Huawei, HiSilicon |
R4-2015608 |
Discussion on applicability rules for different scenarios |
Huawei, HiSilicon |
R4-2015814 |
Applicability rule for PDSCH demodulation requirements in HST WI |
Ericsson |
R4-2017548 |
CR on applicability rules for HST scenarios |
Huawei, HiSilicon |
7.15.3.2 |
BS demodulation requirements [NR_HST-Perf] |
|
R4-2014397 |
Summary of ideal and impairment results for NR HST demodulation requirements |
CATT |
R4-2015183 |
Rel-16 NR HST BS demodulation requirements |
ZTE Wistron Telecom AB |
R4-2017425 |
Email discussion summary for [97e][327] NR_HST_Demod_BS |
Moderator (Nokia) |
R4-2017550 |
WF on Rel-16 NR HST BS demodulation requirements |
Nokia |
R4-2017557 |
Summary of ideal and impairment results for NR HST demodulation requirements |
CATT |
R4-2017625 |
Email discussion summary for [97e][327] NR_HST_Demod_BS |
Moderator (Nokia) |
R4-2017676 |
WF on Rel-16 NR HST BS demodulation requirements |
Nokia |
7.15.3.2.1 |
PUSCH requirements [NR_HST-Perf] |
|
R4-2014398 |
Simulation results for NR HST PUSCH demodulation requirement |
CATT |
R4-2014555 |
Simulation results for NR HST PUSCH |
Intel Corporation |
R4-2014822 |
CR for TS 38.141-1: Updates of NR PUSCH performance requirements for Multi-path fading channel models under high Doppler values and applicability rules. |
NTT DOCOMO, INC. |
R4-2015090 |
On NR Rel-16 HST BS demodulation PUSCH requirements and simulation results |
Nokia, Nokia Shanghai Bell |
R4-2015091 |
CR for 38.104: HST PUSCH demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2015118 |
Simulation results for NR HST PUSCH |
Samsung |
R4-2015609 |
Simulation results on the NR HST PUSCH performance requirements |
Huawei, HiSilicon |
R4-2015846 |
Additional test cases and FRC tables for HST PUSCH |
Ericsson |
R4-2015850 |
simulation results for HST PUSCH under fading channel |
Ericsson |
R4-2017551 |
CR for TS 38.141-1: Updates of NR PUSCH performance requirements for Multi-path fading channel models under high Doppler values and applicability rules. |
NTT DOCOMO, INC. |
R4-2017552 |
CR for 38.104: HST PUSCH demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2017553 |
Additional test cases and FRC tables for HST PUSCH |
Ericsson |
7.15.3.2.2 |
PRACH requirements [NR_HST-Perf] |
|
R4-2014399 |
Simulation results for NR HST PRACH demodulation requirement |
CATT |
R4-2014554 |
Simulation results for NR HST PRACH |
Intel Corporation |
R4-2015092 |
On NR Rel-16 HST BS demodulation PRACH simulation results |
Nokia, Nokia Shanghai Bell |
R4-2015120 |
Simulation results for NR HST PRACH |
Samsung |
R4-2015664 |
CR for 38.104: Introduction of performance requirements for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2015665 |
CR for 38.141-1: Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2015666 |
CR for 38.141-2: Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2015667 |
Simulation results for NR HST PRACH format 0 with restricted set A and B under fading channel |
Huawei, HiSilicon |
R4-2015849 |
simulation results for HST PRACH under fading channel |
Ericsson |
R4-2016596 |
CR for 38.141-1 Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2016597 |
CR for 38.141-2 Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2017554 |
CR for 38.104: Introduction of performance requirements for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2017555 |
CR for 38.141-1 Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
R4-2017556 |
CR for 38.141-2 Introduction of conformance testing for NR HST PRACH under fading channel |
Huawei, HiSilicon |
7.15.3.2.3 |
UL timing adjustment requirements [NR_HST-Perf] |
|
R4-2014400 |
Simulation results for NR PUSCH UL timing adjustment demodulation requirement |
CATT |
R4-2014426 |
Discussion on remaining issues of PUSCH UL TA |
CATT |
R4-2014427 |
CR for 38.141-2: Introduction of NR PUSCH UL timing adjustment performance requirement for scenario X |
CATT |
R4-2014702 |
Discussion on remaining issues for NR HST BS demodulation |
CMCC |
R4-2014823 |
Views on NR PUSCH for UL timing adjustment |
NTT DOCOMO, INC. |
R4-2015093 |
On NR Rel-16 HST BS demodulation UL timing adjustment requirements and simulation results |
Nokia, Nokia Shanghai Bell |
R4-2015119 |
Discussion and simulation results for NR HST UL timing adjustment |
Samsung |
R4-2015121 |
CR on UL timing adjustment conducted performance requirement for TS 38.141-1 |
Samsung |
R4-2015610 |
Discussion and simulation results on the UL timing adjustment |
Huawei, HiSilicon |
R4-2015847 |
discussion on HST UL TA remain issues |
Ericsson |
R4-2015848 |
additional simulation results for UL TA |
Ericsson |
R4-2016468 |
Simulation results for NR HST UL TA |
Intel Corporation |
R4-2017558 |
CR for 38.141-2: Introduction of NR PUSCH UL timing adjustment performance requirement for scenario X |
CATT |
R4-2017559 |
CR on UL timing adjustment conducted performance requirement for TS 38.141-1 |
Samsung |
7.16 |
NR performance requirement enhancement [NR_perf_enh-Perf] |
|
R4-2017426 |
Email discussion summary for [97e][328] NR_perf_enh_Demod |
Moderator (China Telecomm) |
R4-2017560 |
Way forward on release independent aspect for UE demodulation and CSI reporting requirements |
Huawei, HiSilicon |
R4-2017561 |
Way forward on PDSCH CA normal demodulation requirements |
Intel |
R4-2017562 |
Way forward on PMI reporting requirements for Tx ports larger than 8 and up to 32 |
Ericsson, Samsung |
R4-2017563 |
Simulation assumptions for NR PMI reporting requirements for more than 8 Tx ports |
Ericsson |
R4-2017570 |
Way forward on UE power imbalance requirements for FR1 CA and EN-DC |
NTT DoCoMo |
R4-2017573 |
Way forward on CA CQI reporting requirements |
China Telecomm |
R4-2017626 |
Email discussion summary for [97e][328] NR_perf_enh_Demod |
Moderator (China Telecomm) |
R4-2017681 |
Way forward on PMI reporting requirements for Tx ports larger than 8 and up to 32 |
Ericsson, Samsung |
7.16.1.1 |
NR CA PDSCH requirements [NR_perf_enh-Perf] |
|
R4-2014498 |
Test applicability for NR CA PDSCH normal demodulation requirements |
China Telecom |
R4-2014549 |
Discussion on NR CA UE demodulation requirements |
Intel Corporation |
R4-2014550 |
Draft CR on FRC for Normal NR CA demodulation requirements |
Intel Corporation |
R4-2014729 |
Introduction of NR PDSCH FR1 CA 2Rx performance requirements |
CMCC |
R4-2014730 |
Test applicability rule for NR CA PDSCH normal demodulation |
CMCC |
R4-2015312 |
Views on test applicability rule for CA PDSCH requirements |
NTT DOCOMO, INC. |
R4-2015655 |
Discussion on PDSCH CA normal demodulation requirements |
Huawei, HiSilicon |
R4-2015656 |
CR: Introduction of performance requirements for NR FR1 PDSCH CA with 4Rx |
Huawei, HiSilicon |
R4-2016003 |
CR on Applicability rules for Normal NR CA demodulation requirements |
Intel Corporation |
R4-2016512 |
CR on FR2 PDSCH CA Requirements |
Qualcomm Incorporated |
R4-2017566 |
CR on Applicability rules for Normal NR CA demodulation requirements |
Intel Corporation |
R4-2017567 |
Introduction of NR PDSCH FR1 CA 2Rx performance requirements |
CMCC |
R4-2017568 |
CR: Introduction of performance requirements for NR FR1 PDSCH CA with 4Rx |
Huawei, HiSilicon |
7.16.1.2 |
PMI reporting requirements with larger number of Tx ports [NR_perf_enh-Perf] |
|
R4-2014252 |
On PMI reporting requirements with larger number of TX ports |
Apple |
R4-2014551 |
Discussion on PMI Type I requirements |
Intel Corporation |
R4-2014672 |
On PMI reporting requirements for larger Tx ports |
China Telecom |
R4-2014746 |
Views and simulation results for Rel-15 Type II PMI test case |
Samsung |
R4-2014748 |
Draft CR for introduction of Rel-15 Type II PMI test cases |
Samsung |
R4-2015657 |
Simulaiton results for Type II codebook PMI reporting test |
Huawei, HiSilicon |
R4-2015658 |
Discussion on the open issue of PMI reporting test with larger Tx ports |
Huawei, HiSilicon |
R4-2015659 |
CR for TS 38.101-4: Applicability for NR PMI requirements with Tx ports larger than 8 and up to 32 |
Huawei, HiSilicon |
R4-2016098 |
Summary of simulation results of NR UE CSI PMI with 16, and 32Tx antennas |
Ericsson |
R4-2016099 |
Simulation results for Rel-15 Type II codebook |
Ericsson |
R4-2016100 |
Evaluations of Rel-15 Type II PMI testing |
Ericsson |
R4-2016434 |
Parameters and simulation results on PMI reporting requirements with larger number of Tx ports |
Qualcomm Incorporated |
R4-2017569 |
Draft CR for introduction of Rel-15 Type II PMI test cases |
Samsung |
R4-2017660 |
CR to TS 38.101-4: on gamma values for SP Type I PMI requirements |
Ericsson |
7.16.1.3 |
FR1 CA and EN-DC power imbalance requirements [NR_perf_enh-Perf] |
|
R4-2014499 |
Power imbalance requirements for FR1 CA and EN-DC |
China Telecom |
R4-2015317 |
Views on FR1 power imbalance requirements |
NTT DOCOMO, INC. |
R4-2015318 |
CR: FR1 EN-DC power imbalance requirements |
NTT DOCOMO, INC, SoftBank Corp. |
R4-2015660 |
Discussion on UE power imbalance requirements for FR1 CA and EN-DC |
Huawei, HiSilicon |
R4-2015661 |
CR: Addition of power imbalance requirements for intra-band contiguous CA and intra-band EN-DC |
Huawei, HiSilicon |
R4-2015820 |
PDSCH demodulation requirements with power imbalanced condition |
Ericsson |
R4-2016463 |
Views on Power Imbalance Tests |
Qualcomm Incorporated |
R4-2017571 |
CR: FR1 EN-DC power imbalance requirements |
NTT DOCOMO, INC, SoftBank Corp. |
R4-2017572 |
CR: Addition of power imbalance requirements for intra-band contiguous CA and intra-band EN-DC |
Huawei, HiSilicon |
7.16.1.4 |
NR CA CQI reporting requirements [NR_perf_enh-Perf] |
|
R4-2014500 |
Duplex mode and SCS for CA CQI test |
China Telecom |
R4-2014552 |
Discussion on FR1 CA and EN-DC power imbalance requirements |
Intel Corporation |
R4-2014673 |
DraftCR: Adding applicability and requirements for FR1 and FR2 CA CQI reporting test |
China Telecom |
R4-2014728 |
Discussion on FR1 CA and EN-DC power imbalance requirements |
CMCC |
R4-2015662 |
Discussion on CA CQI reporting requirements |
Huawei, HiSilicon |
R4-2015821 |
CA CQI reporting requirements |
Ericsson |
7.16.1.5 |
Release independent [NR_perf_enh-Perf] |
|
R4-2014253 |
On Release Independence for NR UE performance enhancement requirements |
Apple |
R4-2014501 |
Draft CR for TS 38.307 on UE demodulation performance requirements (Rel-15) |
China Telecom |
R4-2014502 |
Draft CR for TS 38.307 on UE demodulation performance requirements (Rel-16) |
China Telecom |
R4-2015316 |
Views on release independence aspect for power imbalance requirements |
NTT DOCOMO, INC. |
R4-2015663 |
Discussion on release independence for NR performance requirements enhancements |
Huawei, HiSilicon |
R4-2015822 |
Release independent requirements for Rel-16 performance requirement enhancement |
Ericsson |
R4-2017564 |
Draft CR for TS 38.307 on UE demodulation performance requirements (Rel-15) |
China Telecom |
R4-2017565 |
Draft CR for TS 38.307 on UE demodulation performance requirements (Rel-16) |
China Telecom |
7.16.2 |
BS demodulation requirements (38.104) [NR_perf_enh-Perf] |
|
R4-2015845 |
Adding FRC table description in Annex in TS38.104 v16.5.0 |
Ericsson |
R4-2017574 |
Adding FRC table description in Annex in TS38.104 v16.5.0 |
Ericsson |
7.17.1 |
General [OTA_BS_testing-Perf] |
|
R4-2015960 |
CR to TR 37.941: overall TR cleanup, Rel-15 |
Huawei |
R4-2015961 |
CR to TR 37.941: overall TR cleanup, Rel-16 |
Huawei |
R4-2017409 |
Email discussion summary for [97e][311] OTA_BS_Testing |
Moderator (Huawei) |
R4-2017575 |
CR to TR 37.941: overall TR cleanup, Rel-15 |
Huawei |
R4-2017627 |
Email discussion summary for [97e][311] OTA_BS_Testing |
Moderator (Huawei) |
R4-2017683 |
CR to TR 37.941: overall TR cleanup, Rel-15 |
Huawei |
7.17.2 |
MU / TT values: derivation and tables [OTA_BS_testing-Perf] |
|
R4-2015714 |
CR to TR 37.941: Removal of Square Brackets |
Ericsson |
R4-2015715 |
CR to TR 37.941: Removal of Square Brackets |
Ericsson |
R4-2015962 |
CR to TR 37.941: MU and TT values alignments and corrections, Rel-15 |
Huawei |
R4-2015963 |
CR to TR 37.941: MU and TT values alignments and corrections, Rel-16 |
Huawei |
R4-2016370 |
Plane Wave Synthesizer |
ROHDE & SCHWARZ |
R4-2016466 |
CR to TR 37.941: Completion of MU terms for PWS. |
ROHDE & SCHWARZ |
R4-2016467 |
Mirror CR to TR 37.941: Completion of MU terms for PWS. |
ROHDE & SCHWARZ |
R4-2017577 |
CR to TR 37.941: Completion of MU terms for PWS. |
ROHDE & SCHWARZ |
R4-2017579 |
CR to TR 37.941: MU and TT values alignments and corrections, Rel-15 |
Huawei |
7.17.3 |
Annexes [OTA_BS_testing-Perf] |
|
R4-2015964 |
CR to TR 37.941: alignments and corrections to the MU contributors and MU derivations, Rel-15 |
Huawei |
R4-2015965 |
CR to TR 37.941: alignments and corrections to the MU contributors and MU derivations, Rel-16 |
Huawei |
R4-2017578 |
CR to TR 37.941: alignments and corrections to the MU contributors and MU derivations, Rel-15 |
Huawei |
R4-2017684 |
CR to TR 37.941: alignments and corrections to the MU contributors and MU derivations, Rel-15 |
Huawei |
7.17.4 |
Others [OTA_BS_testing-Perf] |
|
R4-2016290 |
CR to TR 37.941: Corrections to TRP measurement procedures |
Nokia, Nokia Shanghai Bell |
R4-2016291 |
CR to TR 37.941: Corrections to TRP measurement procedures |
Nokia, Nokia Shanghai Bell |
R4-2016292 |
Justification for additional test cases for PWS |
ROHDE & SCHWARZ |
R4-2016293 |
CR to TR 37.941: Additional test cases for PWS |
ROHDE & SCHWARZ |
R4-2016300 |
Mirror CR to TR 37.941: Additional test cases for PWS |
ROHDE & SCHWARZ |
R4-2017576 |
CR to TR 37.941: Corrections to TRP measurement procedures |
Nokia, Nokia Shanghai Bell |
7.18.1 |
RRM core requirements maintenance (38.133) [NR_2step_RACH-Core] |
|
R4-2014935 |
CR Maintenance 2-step RACH RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2017023 |
Email discussion summary for [97e][224] NR_2step_RACH_RRM |
Moderator (ZTE Corporation) |
R4-2017255 |
CR Maintenance 2-step RACH RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2017294 |
Email discussion summary for [97e][224] NR_2step_RACH_RRM |
Moderator (ZTE Corporation) |
7.18.2 |
RRM perf. requirements (38.133) [NR_2step_RACH-Perf] |
|
R4-2017254 |
WF on 2-step RACH RRM test cases |
ZTE Corporation |
7.18.2.1 |
General [NR_2step_RACH-Perf] |
|
R4-2014356 |
Principles for 2-step RACH test cases |
ZTE Corporation |
R4-2014933 |
Big CR on 2-step RA type RRM performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2014934 |
2-step RACH RRM performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2015810 |
Draft CR: RMC of MsgA for 2-step RACH test |
Ericsson |
R4-2017253 |
Big CR on 2-step RA type RRM performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2017259 |
Draft CR: RMC of MsgA for 2-step RACH test |
Ericsson |
7.18.2.2 |
Test cases [NR_2step_RACH-Perf] |
|
R4-2014008 |
[draft CR] 2-step RACH test case |
ZTE Corporation |
R4-2014936 |
Draft CR on 2-step RA type CBRA in FR2 for NR Standalone |
Nokia, Nokia Shanghai Bell |
R4-2015303 |
Draft CR on TC for 2-step RA type contention based RA in FR1 and FR2 NR cells for EN-DC |
NEC |
R4-2015811 |
Draft CR: Introduction of 2-step RACH CFRA tests |
Ericsson |
R4-2017256 |
[draft CR] 2-step RACH test case |
ZTE Corporation |
R4-2017257 |
Draft CR on 2-step RA type CBRA in FR2 for NR Standalone |
Nokia, Nokia Shanghai Bell |
R4-2017258 |
Draft CR on TC for 2-step RA type contention based RA in FR1 and FR2 NR cells for EN-DC |
NEC |
R4-2017260 |
Draft CR: Introduction of 2-step RACH CFRA tests |
Ericsson |
7.18.3 |
BS Demodulation requirements (38.104) [NR_2step_RACH-Perf] |
|
R4-2014560 |
Views on BS demodulation requirements for NR 2-Step RACH |
Intel Corporation |
R4-2014561 |
CR to TS 38.141-2: BS demodulation requirements for 2-step RACH (Annex) |
Intel Corporation |
R4-2014937 |
2-step RACH BS demodulation performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2014938 |
2-step RACH BS demodulation simulation results |
Nokia, Nokia Shanghai Bell |
R4-2014939 |
Introduction of 2-step RACH FRC tables in 38.141-1 |
Nokia, Nokia Shanghai Bell |
R4-2015022 |
Introduction of test procedure and requirement for 2-step RACH |
Ericsson |
R4-2015125 |
Discussion and simulation results for BS 2-step RACH requirement |
Samsung |
R4-2015126 |
Draft CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
Samsung |
R4-2015177 |
Draft CR to TS 38.104 BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2015178 |
Simulation results on BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2015179 |
Simulation results collection on BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2015180 |
Open issues on BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2015611 |
Discussion and simulation results on NR 2-step RACH BS performance requirements |
Huawei, HiSilicon |
R4-2015612 |
CR on BS demodulation requirements for 2-step RACH for FR2 |
Huawei, HiSilicon |
R4-2015857 |
2-step RACH open issues |
Ericsson |
R4-2015858 |
2-step RACH simulation results |
Ericsson |
R4-2017427 |
Email discussion summary for [97e][329] NR_2step_RACH_Demod |
Moderator (ZTE) |
R4-2017580 |
Way forward on BS performance requirements for 2-step RACH |
ZTE |
R4-2017628 |
Email discussion summary for [97e][329] NR_2step_RACH_Demod |
Moderator (ZTE) |
R4-2017633 |
CR to TS 38.141-2: BS demodulation requirements for 2-step RACH (Annex) |
Intel Corporation |
R4-2017634 |
Draft CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
Samsung |
R4-2017635 |
CR to TS 38.104 BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2017636 |
CR on BS demodulation requirements for 2-step RACH for FR2 |
Huawei, HiSilicon |
R4-2017637 |
Introduction of 2-step RACH FRC tables in 38.141-1 |
Nokia, Nokia Shanghai Bell |
R4-2017638 |
Introduction of test procedure and requirement for 2-step RACH |
Ericsson |
R4-2017653 |
CR on MsgA PUSCH radiated performance requirement for TS 38.141-2 |
Samsung |
R4-2017654 |
CR to 38.141-1 Introduction of test procedure and requirements for 2-step RACH |
Ericsson |
R4-2017666 |
CR to TS 38.104 BS demodulation requirements for 2-step RACH |
ZTE Wistron Telecom AB |
R4-2017667 |
CR to 38.141-1 Introduction of test procedure and requirements for 2-step RACH |
Ericsson |
7.19.1 |
UE transient period capability [TEI16] |
|
R4-2014489 |
Short Transient Period Testing |
Qualcomm Incorporated |
R4-2014490 |
Draft CR on introduction of shorter Transient Period Capability |
Qualcomm Incorporated, Verizon, Dish Network, Ericsson, CMCC, Keysight Technologies, Nokia, Nokia Shanghai Bell, AT&T, ZTE, Vodafone, Orange, T-Mobile USA, Deutsche Telekom, Telecom Italia, CHTTL, China Telecom, SGS Wireless, Interdigital |
R4-2016516 |
On transient period UE capability |
Huawei, HiSilicon |
R4-2016517 |
CR on TS 38.101-1 time mask for shorter transient |
Huawei, HiSilicon |
R4-2016616 |
Email discussion summary for [97e][114] NR_transient_period |
Moderator (CMCC) |
R4-2016829 |
CR on TS 38.101-1 time mask for shorter transient |
Huawei, HiSilicon |
R4-2016958 |
Email discussion summary for [97e][114] NR_transient_period |
Moderator (CMCC) |
7.19.2 |
Transmit diversity and power class related to UL MIMO [TEI16] |
|
R4-2016617 |
Email discussion summary for [97e][115] NR_TxD |
Moderator (vivo) |
R4-2016830 |
WF on NR TxD |
vivo |
R4-2016959 |
Email discussion summary for [97e][115] NR_TxD |
Moderator (vivo) |
7.19.2.1 |
R16 support of transmit diversity [TEI16] |
|
R4-2014303 |
Remaining issues on Tx diversity |
LG Electronics Polska |
R4-2014583 |
Remaining Issues on Transparent TxD |
Intel Corporation |
R4-2014686 |
Remaining items on transparent Tx diversity |
Anritsu corporation |
R4-2014712 |
Tx diversity changes for Rel-16 |
Qualcomm Incorporated |
R4-2014713 |
Introduction of Tx diversity in tor 38101-1 |
Qualcomm Incorporated |
R4-2014849 |
Further discussio on the Support of Transparent Tx Diversity in Rel-16 |
Samsung |
R4-2014904 |
On Tx diversity |
Apple Inc. |
R4-2015265 |
Discussion on Tx diversity open issues |
Xiaomi |
R4-2015321 |
Remaining issues in Transparent Tx Diversity |
vivo |
R4-2015340 |
Discussion on Rel-16 TxD |
OPPO |
R4-2015341 |
CR on TxD requirements |
OPPO |
R4-2015342 |
Reply LS on Tx diversity testing |
OPPO |
R4-2016034 |
Discussion on remaining open issues for Tx diversity requirements |
Rohde & Schwarz |
R4-2016285 |
On the EVM Definition for Transmit Diversity |
Motorola Mobility France S.A.S |
R4-2016288 |
On the EVM Definition for Transmit Diversity |
Lenovo, Motorola Mobility |
R4-2016477 |
On Tx diversity requirements |
Huawei, HiSilicon |
R4-2016478 |
CR for TS 38.101-1 Tx diversity requirements |
Huawei, HiSilicon |
7.19.2.2 |
Power class related to UL MIMO and other related req. (MPR, SEM, etc) [TEI16 or NR_newRAT-Core] |
|
R4-2015322 |
Remaining issues in Power class |
vivo |
R4-2015976 |
PHR and Pcmax verification for NR PC2 devices supporting NR PC3 for EN-DC |
Ericsson |
R4-2015977 |
Correction of Pcmax for an NR PC2 UE supporting NR PC3 for EN-DC |
Ericsson |
R4-2016465 |
Discussion on Single Carrier MPR versus Architecture |
Skyworks Solutions Inc. |
R4-2016479 |
Discussion and draft reply LS on EN-DC power class |
Huawei, HiSilicon |
7.19.3 |
Other UE RF [WI code or TEI16] |
|
R4-2014167 |
CR CatF n7 NS_46 AMPR and coexistence |
Qualcomm Incorporated |
R4-2014168 |
CR CatF CA_n39-n41_and CA_n40-n41 Sync |
Qualcomm Incorporated |
R4-2014169 |
CR CatF Cross Band Noise DC_3_n1_highBW |
Qualcomm Incorporated |
R4-2014170 |
ENDC Cross Band Noise with high NR BW |
Qualcomm Incorporated |
R4-2014317 |
Consideration on additional ILs and MSD levels for DC_20_n38 UE or V2X_20_n38 UE based on RF architecture |
LG Electronics France |
R4-2014318 |
Correction on Additional ILs and MSD levels for DC_20_n38 UE |
LG Electronics France, Huawei |
R4-2014319 |
Discussion on MFBI for NR system |
LG Electronics France |
R4-2014517 |
n53 bracket removal |
Nokia |
R4-2014520 |
TS 38.101-3: Addition of missing lower order fallbacks |
Nokia, AT&T |
R4-2014521 |
TR 37.716-21-11: Addition of missing lower order fallbacks |
Nokia, AT&T |
R4-2014582 |
CR to 38.101-3 (Rel-16) error correntions to configurations for CA and DC |
Intel Corporation |
R4-2014600 |
CR on adding NR ovelapping bands list in TS38.307 in Rel-15 |
LG Electronics France |
R4-2014620 |
CR on adding NR ovelapping bands list in TS38.307 in Rel-16 |
LG Electronics France |
R4-2014883 |
Clarification on RF assumption for B42_n77 and B42_n78 |
NTT DOCOMO INC. |
R4-2014899 |
Coexistence cleanup for 38.101-1 Rel16 |
Apple Inc. |
R4-2014901 |
Coexistence cleanup for 38.101-3 Rel16 |
Apple Inc. |
R4-2014915 |
CR for TS 38.101-3: Corrections for intra-band contiguous EN-DC configurations |
Apple Inc. |
R4-2014957 |
CR to TS 38.101-2 on fallback group for intra-band contiguous CA (Rel-16) |
ZTE Corporation |
R4-2015033 |
CR to TS38.101-1: Correction on the general requirement and configured transmitted power requirement for inter-band DC |
ZTE Corporation |
R4-2015042 |
Discussion on the MSD of the new channel BW for EN-DC and NR CA band combinations |
ZTE Corporation |
R4-2015264 |
CR to TS 38.101-3: corrections on ACS for intra-band contiguous EN-DC |
Xiaomi |
R4-2015299 |
Editorial correction on section 5.2C to 38.101-1 R16 |
Huawei, HiSilicon |
R4-2015323 |
Alignment of descritpion of the power class restriction for inter-band EN-DC |
vivo |
R4-2015324 |
Correction of delta Powerclass for Inter-band EN-DC |
vivo, CMCC, China Unicom |
R4-2015331 |
CR on NR power class under EN-DC |
OPPO |
R4-2015332 |
Discussion on WRC-19 requirements |
OPPO |
R4-2015336 |
CR on FR2 equal PSD in UL CA (R16) |
OPPO |
R4-2015339 |
CR on sum of power for multiple transmit connectors |
OPPO |
R4-2015552 |
Consideration on Cross band isolation impact with larger BW |
Huawei, HiSilicon |
R4-2015553 |
Discussion on spurious emission about UE co-existence between band n40 and n41 |
Huawei, HiSilicon, CMCC |
R4-2015554 |
CR on spurious emission about UE co-existence between band n40 and n41 |
Huawei, HiSilicon, CMCC |
R4-2015555 |
Discussion on asynchronous for DC_42_n79 |
Huawei, HiSilicon |
R4-2015557 |
CR for 38.101-1 to correct the notation of SUL band combinations in order to be aligned with 38.101-3 |
Huawei, HiSilicon |
R4-2015699 |
Reference measurement channels for 70 MHz CBW |
Huawei, HiSilicon |
R4-2015729 |
CR to TS 38.101-3 corrections on inter-band EN-DC configurations including FR1 and FR2 |
CHTTL |
R4-2015795 |
Discussion on handling the cross band isolation requirement for larger channel BW in Rel.16 |
CHTTL |
R4-2015856 |
CR to TS 38.307 on release independent update for the Rel.16 EN-DC and NR CA/DC |
CHTTL, ZTE Corporation, Dish, SGS Wireless |
R4-2015914 |
Correction to supported channel bandwidths per SUL_n41A-n81A |
Keysight Technologies UK Ltd |
R4-2015978 |
Modification of FR2 MOP verification with account of the 38.213 scaling rule |
Ericsson |
R4-2015979 |
Correction to Pcmax: account of power prioritization rules for secondary cells |
Ericsson |
R4-2015980 |
Correction to modified MPR behaviour |
Ericsson |
R4-2015981 |
Verification of the P-MPR method for EN-DC FDD-TDD power class 2 |
Ericsson |
R4-2016341 |
CR for editorial corrections 38.101-1 |
Ericsson |
R4-2016342 |
CR for editorial corrections 38.101-2 |
Ericsson |
R4-2016343 |
CR for editorial corrections 38.101-3 |
Ericsson |
R4-2016442 |
Replacement of void sub-clauses |
Qualcomm Incorporated |
R4-2016451 |
CR to for 38.101-1: CA uplink power clarification |
T-Mobile USA |
R4-2016458 |
CR for 38.101-1: Editorial corrections |
T-Mobile USA |
R4-2016483 |
CR for TS 38.101-1: harmonic MSD for CA_n41-n79 |
Huawei, HiSilicon |
R4-2016592 |
Editorial CR to change |
Qualcomm Incorporated |
R4-2016593 |
Editorial CR to change |
Qualcomm Incorporated |
R4-2016618 |
Email discussion summary for [97e][116] NR_R16_Maintenance |
Moderator (OPPO) |
R4-2016831 |
WF on unsynchronized NW between n40 and n41 |
Huawei |
R4-2016832 |
TS 38.101-3: Addition of missing lower order fallbacks |
Nokia, AT&T |
R4-2016833 |
TR 37.716-21-11: Addition of missing lower order fallbacks |
Nokia, AT&T |
R4-2016834 |
CR on sum of power for multiple transmit connectors |
OPPO |
R4-2016835 |
Replacement of void sub-clauses |
Qualcomm Incorporated |
R4-2016836 |
CR for TS 38.101-1: harmonic MSD for CA_n41-n79 |
Huawei, HiSilicon |
R4-2016837 |
CR to TS 38.101-2 on fallback group for intra-band contiguous CA (Rel-16) |
ZTE Corporation |
R4-2016838 |
CR for editorial corrections 38.101-2 |
Ericsson |
R4-2016839 |
WF on handling of interference caused by larger CBWs |
Qualcomm |
R4-2016840 |
WF on DC_20A_n38A RF architecture |
LGE |
R4-2016841 |
WF on simultaneous Rx/Tx for DC_42_n79 |
Huawei |
R4-2016842 |
CR on NR power class under EN-DC |
OPPO |
R4-2016843 |
CR for editorial corrections 38.101-3 |
Ericsson |
R4-2016846 |
CR on adding NR ovelapping bands list in TS38.307 in Rel-15 |
LG Electronics France |
R4-2016847 |
CR on adding NR ovelapping bands list in TS38.307 in Rel-16 |
LG Electronics France |
R4-2016848 |
CR to TS 38.307 on release independent update for the Rel.16 EN-DC and NR CA/DC |
CHTTL, ZTE Corporation, Dish, SGS Wireless |
R4-2016960 |
Email discussion summary for [97e][116] NR_R16_Maintenance |
Moderator (OPPO) |
R4-2016989 |
CR for editorial corrections 38.101-1 |
Ericsson |
R4-2017804 |
CR CatF n7 NS_46 AMPR and coexistence |
Qualcomm Incorporated |
R4-2017818 |
Correction on Additional ILs and MSD levels for DC_20_n38 UE |
LG Electronics France, Huawei |
7.19.4 |
BS RF [WI code or TEI16] |
|
R4-2015966 |
CR to TR 38.820: correction in the NF analysis for NR BS, Rel-16 |
Huawei |
R4-2015967 |
CR to TS 37.105: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-16 |
Huawei |
R4-2015968 |
CR to TS 37.145-1: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-16 |
Huawei |
R4-2015969 |
CR to TS 37.145-2: Introduction of new BS capability set for NR+EUTRA+UTRA, Rel-16 |
Huawei |
R4-2016206 |
CR to 38.141-2: Correction to test system uncertainty |
Nokia, Nokia Shanghai Bell |
R4-2016430 |
CR to TS 37.105: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2016431 |
CR to TS 37.145-1: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2016432 |
CR to TS 37.145-2: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2017432 |
CR to TS 37.105: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2017433 |
CR to TS 37.145-1: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2017434 |
CR to TS 37.145-2: addition of the OBUE applicability table, Rel-15 |
Huawei |
R4-2017668 |
CR to TS 37.105: addition of the OBUE applicability table, Rel-16 |
Huawei |
R4-2017669 |
CR to TS 37.145-1: addition of the OBUE applicability table, Rel-16 |
Huawei |
R4-2017670 |
CR to TS 37.145-2: addition of the OBUE applicability table, Rel-16 |
Huawei |
7.19.5 |
RRM [WI code or TEI16] |
|
R4-2014280 |
Discussion on R16 IDLE/INACTIVE RRM requirement with SMTC2-LP |
Apple |
R4-2014281 |
CR on R16 IDLE/INACTIVE RRM requirement with SMTC2-LP |
Apple |
R4-2014378 |
CR on TS38.133 for E-UTRAN |
MediaTek inc. |
R4-2014379 |
CR on TS38.133 for SCell activation and deactivation delay test cases |
MediaTek inc. |
R4-2014671 |
Fine/rough beam assumption for CLI performance test cases |
LG Electronics Inc. |
R4-2014796 |
CR on interruptions at E-UTRA SRS carrier based switching in TS38.133 |
OPPO |
R4-2015477 |
CR on maintaining L1-RSRP measurements test cases R16 |
Huawei, HiSilicon |
R4-2015478 |
Discussion on MRTD/MTTD requirements for FR1 intra-band NCCA |
Huawei, HiSilicon |
R4-2015479 |
CR on MRTD/MTTD requirements for FR1 intra-band NCCA R16 |
Huawei, HiSilicon |
R4-2015533 |
Update NR Frequency Band Groups to include Band n48 |
Huawei, HiSilicon |
R4-2015534 |
Update NR Frequency Band Groups to include Band n65 |
Huawei, HiSilicon |
R4-2015671 |
[CR] NR Perf Maintenance R16 Cat F |
ZTE Corporation |
R4-2015792 |
[CR] Specify RRC processing delay in TCI state switching delay for R16 NR-U |
ZTE Corporation |
R4-2015878 |
Correcting the range of Lmax=8 for unpaired spectrum |
Nokia, Nokia Shanghai Bell |
R4-2017003 |
Email discussion summary for [97e][204] R16_NR_RRM_maintenance |
Moderator (Apple) |
R4-2017067 |
CR on interruptions at E-UTRA SRS carrier based switching in TS38.133 |
OPPO |
R4-2017274 |
Email discussion summary for [97e][204] R16_NR_RRM_maintenance |
Moderator (Apple) |
7.19.7 |
NR MIMO OTA test methods (38.827) [FS_NR_MIMO_OTA_test] |
|
R4-2014289 |
Addition of Time Domain Alternative for Spatial Correlation Validation |
Spirent Communications |
R4-2016211 |
Update of FR2 probe configuration |
Keysight Technologies UK Ltd |
R4-2016227 |
Number of Slots for NR MIMO OTA testing |
vivo, CAICT |
R4-2016228 |
Number of Slots for NR MIMO OTA testing |
vivo, CAICT |
R4-2016544 |
TP to 38.827 on channel model rotations |
Huawei, HiSilicon |
R4-2016546 |
pCR to 38.827 on base station beamforming configuration |
Huawei, HiSilicon |
R4-2016586 |
CR for 38.827 on corrections |
Huawei, HiSilicon |
R4-2017581 |
Addition of Time Domain Alternative for Spatial Correlation Validation |
Spirent Communications |
R4-2017582 |
Number of Slots for NR MIMO OTA testing |
vivo, CAICT |
R4-2017639 |
TP to 38.827 on channel model rotations |
Huawei, HiSilicon |
R4-2017640 |
CR to 38.827 on base station beamforming configuration |
Huawei, HiSilicon |
R4-2017641 |
CR for 38.827 on corrections |
Huawei, HiSilicon |
R4-2017658 |
Addition of Time Domain Alternative for Spatial Correlation Validation |
Spirent Communications |
8 |
Rel-16 UE feature list |
|
R4-2014234 |
On R16 UE feature list |
Apple |
R4-2014483 |
On the Optionality of RAN4 Requirements |
Qualcomm Incorporated, CMCC, KDDI, AT&T, Ericsson, Nokia, T-Mobile USA, China Telecom |
R4-2014488 |
Overloading of the Per-FR gap capability |
Qualcomm Incorporated |
R4-2014627 |
Discussion on UE feature list |
MediaTek inc. |
R4-2015089 |
Clarification of intra-bandENDC-Support |
Nokia, Nokia Shanghai Bell |
R4-2015566 |
Views on Rel-16 NR UE feature list |
Intel Corporation |
R4-2015798 |
On NRU operation modes and capabilities |
LG Electronics Finland |
R4-2015982 |
On the FG |
Ericsson |
R4-2016030 |
On the Optionality of RAN4 Requirements |
Qualcomm Incorporated, CMCC, KDDI, AT&T, Ericsson, Nokia, T-Mobile USA, China Telecom, Vodafone, Verizon, Softbank |
R4-2016619 |
Email discussion summary for [97e][117] R16_UE_ feature |
Moderator (CMCC) |
R4-2016849 |
LS on updated Rel-16 RAN4 UE features lists for NR and LTE |
RAN4 |
R4-2016850 |
Updated RAN4 UE features list for Rel-16 |
CMCC |
R4-2016961 |
Email discussion summary for [97e][117] R16_UE_ feature |
Moderator (CMCC) |
R4-2017803 |
LS on Rel-16 mandatory RRM requirements |
RAN4 |
9.1 |
LTE/NR spectrum sharing in band 48/n48 frequency range [NR_n48_LTE_48_coex-Core] |
|
R4-2016620 |
Email discussion summary for [97e][118] NR_n48_LTE_48_coex |
Moderator (Apple) |
R4-2016962 |
Email discussion summary for [97e][118] NR_n48_LTE_48_coex |
Moderator (Apple) |
9.1.2 |
Channel raster, sync raster, and UL shift [NR_n48_LTE_48_coex-Core] |
|
R4-2014174 |
B48/n48 Allocation shift emission containment |
Qualcomm Incorporated |
R4-2014890 |
LTE/NR spectrum sharing in band 48/n48 frequency range |
Apple Inc., Comcast |
R4-2014891 |
Introduction of LTE/NR spectrum sharing in band 48/n48 frequency range |
Apple Inc. |
R4-2015086 |
n48 DSS operation with 100 kHz channel raster shift |
Nokia, Nokia Shanghai Bell |
R4-2015350 |
Views on DSS in band 48/n48 |
OPPO |
R4-2016140 |
LTE/NR spectrum sharing in band 48/n48 frequency range |
Ericsson GmbH, Eurolab |
R4-2016372 |
The remaining issue on n48 DSS |
Google Inc. |
10 |
Rel-17 spectrum related Work Items for NR |
|
R4-2016621 |
Email discussion summary for [97e][119] NR_Baskets_Part_1 |
Moderator (Nokia) |
10.1.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R17_intra-Core /Perf] |
|
R4-2015916 |
Revised WID NR Intra-band Rel-17 |
Ericsson |
R4-2015919 |
CR introduction completed band combinations Rel-17 NR Intra-band - |
Ericsson |
R4-2015920 |
CR introduction completed band combinations Rel-17 NR Intra-band - |
Ericsson |
R4-2015924 |
TR 38.717-01-01 v0.2.0 Rel-17 NR Intra-band |
Ericsson |
10.1.2 |
UE RF for FR1 [NR_CA_R17_intra-Core] |
|
R4-2014493 |
UE Architecture and DL MIMO Aspects for Supporting n77(3A) DL CA |
Skyworks Solutions Inc. SoftBank Corp. |
R4-2015069 |
MSD for CA_n71(2A) |
MediaTek Inc. |
R4-2015431 |
DraftCR for 38.101-1 to add BCS1 for CA_n77(2A) |
Huawei, HiSilicon |
R4-2016329 |
TP to TR 38.717-01-01 to include CA_n2(2A) |
Ericsson, Verizon |
R4-2016330 |
TP to TR 38.717-01-01 to include CA_n5(2A) |
Ericsson, Verizon, MediaTek |
R4-2016331 |
TP to TR 38.717-01-01 to include CA_n77(3A) |
Ericsson, Verizon |
R4-2016332 |
TP to TR 38.717-01-01 to include CA_n77(4A) |
Ericsson, Verizon |
R4-2016339 |
TP to TR 38.717-01-01 to update MSD values CA_n71(2A) |
Ericsson, T-Mobile US |
R4-2016666 |
MSD for CA_n71(2A) |
MediaTek Inc. |
R4-2016679 |
TP to TR 38.717-01-01 to include CA_n5(2A) |
Ericsson, Verizon, MediaTek |
R4-2016913 |
TP to TR 38.717-01-01 to include CA_n77(3A) |
Ericsson, Verizon |
10.2 |
NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) [NR_CADC_R17_2BDL_xBUL] |
|
R4-2016622 |
Email discussion summary for [97e][120] NR_Baskets_Part_2 |
Moderator (Nokia) |
10.2.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R17_2BDL_xBUL-Core/Perf] |
|
R4-2015057 |
Revised WID on Rel-17 NR Inter-band CA_DC xUL_2DL (x=1,2) |
ZTE Corporation |
R4-2015058 |
Draft CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2015059 |
Draft CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2015184 |
TR 38.717-02-01 v0.2.0 |
ZTE Wistron Telecom AB |
R4-2017805 |
CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-1 |
ZTE |
R4-2017806 |
CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-3 |
ZTE |
10.2.2 |
NR inter band CA without any FR2 band(s) [NR_CADC_R17_2BDL_xBUL-Core] |
|
R4-2014110 |
TP for TR 38.717-02-01 CA_n41-n77 |
Samsung, KDDI |
R4-2014111 |
TP for TR 38.717-02-01 CA_n41-n78 |
Samsung, KDDI |
R4-2014131 |
TP for TR 38.717-02-01 CA_n2-n66 |
Samsung, TELUS, Bell mobility |
R4-2014141 |
Draft CR for 38.101-1 to introduce new inter-band CA for 2bands DL with x bands UL(x=1, 2) within FR1 |
Samsung, TELUS, Bell mobility |
R4-2014522 |
draft CR for NR inter-band CA for 2 bands DL |
Nokia, T-Mobile USA |
R4-2014524 |
TP for TR 38.717-02-01: CA_n41-n77 |
Nokia, T-Mobile USA |
R4-2014525 |
TP for TR 38.717-02-01: CA_n71A-n77A |
Nokia, T-Mobile USA |
R4-2014842 |
DraftCR to 38.101-1: Introduce NR CA configurations for CA_n2A-n48 and CA_n48-n66A combinations |
Verizon Denmark |
R4-2014876 |
TP for TR 37.717-02-01: CA_n5-n48 |
Verizon Denmark |
R4-2015045 |
Draft CR to TS38.101-1: Add missing OOB blocking exception combination |
ZTE Corporation |
R4-2015046 |
TP for TR38.717-02-01_ CA_n34A-n79A |
ZTE Corporation |
R4-2015075 |
draftCR for CA_n66(2A)-n77A, CA_n66A-n77(2A) and CA_n66(2A)-n77(2A) BCS1 |
Nokia, Nokia Shanghai Bell |
R4-2015076 |
TP to TR 38.717-02-01: CA_n5-n25 |
Nokia, Nokia Shanghai Bell |
R4-2015077 |
TP to TR 38.717-02-01: CA_n25-n77 |
Nokia, Nokia Shanghai Bell |
R4-2015082 |
TP to TR 38.717-02-01 to correct CA_n7(2A)-n66 BCS |
Nokia, Nokia Shanghai Bell |
R4-2015425 |
DraftCR for 38.101-1 to add BCS1 for CA_n20A-n28A |
Huawei, HiSilicon |
R4-2015426 |
DraftCR for 38.101-1 to add BCS1 for CA_n1A-n78A CA_n1A-n78(2A) |
Huawei, HiSilicon |
R4-2015427 |
DraftCR for 38.101-1 to add BCS1 for CA_n8A-n78A and CA_n8A-n78(2A)_BCS0 |
Huawei, HiSilicon |
R4-2015428 |
TP for TR 38.717-02-01: to add UL configuration for CA_n78A-n79A and CA_n78(2A)-n79A_BCS0 |
Huawei, HiSilicon |
R4-2015429 |
TP for TR 38.717-02-01: CA_n8A-n28A |
Huawei, HiSilicon |
R4-2015430 |
TP for TR 38.717-02-01: CA_n3A-n7A |
Huawei, HiSilicon |
R4-2016680 |
TP for TR 38.717-02-01 CA_n41-n78 |
Samsung, KDDI |
R4-2016681 |
draft CR for NR inter-band CA for 2 bands DL |
Nokia, T-Mobile USA |
R4-2016682 |
TP for TR 38.717-02-01: CA_n41-n77 |
Nokia, T-Mobile USA |
R4-2016683 |
TP for TR 38.717-02-01: CA_n71A-n77A |
Nokia, T-Mobile USA |
R4-2016684 |
TP for TR 37.717-02-01: CA_n5-n48 |
Verizon Denmark |
R4-2016685 |
draftCR for CA_n66(2A)-n77A, CA_n66A-n77(2A) and CA_n66(2A)-n77(2A) BCS1 |
Nokia, Nokia Shanghai Bell |
R4-2016686 |
TP to TR 38.717-02-01: CA_n5-n25 |
Nokia, Nokia Shanghai Bell |
R4-2016687 |
TP to TR 38.717-02-01: CA_n25-n77 |
Nokia, Nokia Shanghai Bell |
R4-2016688 |
DraftCR for 38.101-1 to add BCS1 for CA_n20A-n28A |
Huawei, HiSilicon |
R4-2016689 |
TP for TR 38.717-02-01: to add UL configuration for CA_n78A-n79A and CA_n78(2A)-n79A_BCS0 |
Huawei, HiSilicon |
R4-2016690 |
TP for TR 38.717-02-01: CA_n8A-n28A |
Huawei, HiSilicon |
R4-2016691 |
TP for TR 38.717-02-01: CA_n3A-n7A |
Huawei, HiSilicon |
10.2.3 |
NR inter band CA with at least one FR2 band [NR_CADC_R17_2BDL_xBUL-Core] |
|
R4-2014813 |
draft CR 38.101-3 to add DC_n1-n257 and DC_n79-n257 |
NTT DOCOMO, INC. |
R4-2014843 |
DraftCR to 38.101-3: Introduce inter-band CA and DC configurations including FR2 |
Verizon Denmark |
R4-2015131 |
Draft CR for 38.101-3 to add n78C in DC_n78-n257 |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
R4-2015217 |
draftCR to introduce CADC_n1-n258 to 38.101-3 |
Nokia |
R4-2015218 |
draftCR to introduce CADC_n40-n258 to 38.101-3 |
Nokia |
R4-2015219 |
draftCR to introduce CADC_n78-n258 to 38.101-3 |
Nokia |
R4-2016308 |
CR to add CBW 25, 30 and 70 MHz for n78 in n78-n258 configurations |
Ericsson, Telstra |
R4-2016692 |
DraftCR to 38.101-3: Introduce inter-band CA and DC configurations including FR2 |
Verizon Denmark |
R4-2016693 |
Draft CR for 38.101-3 to add n78C in DC_n78-n257 |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
10.3.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_1BLTE_1BNR_2DL2UL-Core/Perf] |
|
R4-2014786 |
TR 37.717-11-11 v0.2.0 Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2014787 |
Revised WID for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2014788 |
Big CR for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
10.3.2 |
EN-DC without FR2 band [DC_R17_1BLTE_1BNR_2DL2UL-Core] |
|
R4-2014030 |
TP for 37.717-11-11 for DC_8_n2 |
Huawei,HiSilicon |
R4-2014070 |
TP to TR 37.717-11-11: DC_18A_n28A |
KDDI Corporation |
R4-2014142 |
Draft CR for 38.101-3 to introduce new inter-band EN-DC (1NR band +1LTE band) within FR1 |
Samsung, SK Telecom, KT, KDDI, TELUS, Bell mobility |
R4-2014172 |
DC_XXA_71A_n71A REFSENS relaxation |
Qualcomm Incorporated |
R4-2014810 |
TP to TR 37.717-11-11: DC_18A_n41A |
KDDI Corporation |
R4-2014850 |
TP for TR 38.717-11-11: DC_48_n77 |
Verizon Denmark |
R4-2015071 |
draftCR for DC_1A-1A_n28A and DC_1A-1A_n78A |
Nokia, Nokia Shanghai Bell |
R4-2015221 |
TP for 37.717-11-11 to introduce DC_7_n2A |
Nokia |
R4-2015245 |
TP for 37.717-11-11 to introduce DC_71A_n71A |
Nokia, T-Mobile |
R4-2015403 |
TP for TR 37.717-11-11: DC_12_n71 |
Huawei, HiSilicon |
R4-2015928 |
CR to add configurations for 1_n40 and 3_n40 |
Ericsson |
R4-2016304 |
CR to add DC_1_n258 configurations |
Ericsson, Telstra |
R4-2016309 |
CR to add CA_n7B UL configurations |
Ericsson, Telstra |
R4-2016655 |
TP for 37.717-11-11 for DC_8_n2 |
Huawei,HiSilicon |
R4-2016658 |
TP to TR 37.717-11-11: DC_18A_n28A |
KDDI Corporation |
R4-2016661 |
DC_XXA_71A_n71A REFSENS relaxation |
Qualcomm Incorporated |
R4-2016663 |
TP to TR 37.717-11-11: DC_18A_n41A |
KDDI Corporation |
R4-2016667 |
TP for 37.717-11-11 to introduce DC_7_n2A |
Nokia |
R4-2016670 |
TP for 37.717-11-11 to introduce DC_71A_n71A |
Nokia, T-Mobile |
R4-2016676 |
TP for TR 37.717-11-11: DC_12_n71 |
Huawei, HiSilicon |
10.3.3 |
EN-DC with FR2 band [DC_R17_1BLTE_1BNR_2DL2UL-Core] |
|
R4-2014607 |
Draft CR for TS 38.101-3: Support of Uplink n257D/G/H/I for DC_8_n257 and DC_11_n257 |
SoftBank Corp. |
R4-2014844 |
DraftCR to 38.101-3: Introduce configurations for inter-band EN-DC including FR2 |
Verizon Denmark |
R4-2014877 |
TP for TR 37.717-11-11 for DC_2_n261 |
Verizon Denmark |
R4-2015132 |
Draft CR for 38.101-3 to add UL EN-DC configurations for DC_5_n257, DC_7_n257 and DC_7-7_n257 |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
R4-2015220 |
draftCR to introduce DC_8A_n258 to 38.101-3 |
Nokia |
10.4 |
DC of 2 LTE band and 1 NR band [DC_R17_2BLTE_1BNR_3DL2UL] |
|
R4-2014056 |
TP for TR 37.717-21-11: DC_7-32_n78 |
VODAFONE Group Plc |
R4-2014057 |
TP for TR 37.717-21-11: DC_7-32_n1 |
VODAFONE Group Plc |
R4-2014058 |
TP for TR 37.717-21-11: DC_20-32_n1 |
VODAFONE Group Plc |
10.4.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_2BLTE_1BNR_3DL2UL-Core/Perf] |
|
R4-2015704 |
TR 37.717-21-11 V0.2.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
R4-2015705 |
Revised WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2015706 |
CR on introduction of completed EN-DC of 2 bands LTE and 1 band NR from RAN4#96e and RAN4#97e into TS 38.101-3 |
Huawei, HiSilicon |
10.4.2 |
EN-DC without FR2 band [DC_R17_2BLTE_1BNR_3DL2UL-Core] |
|
R4-2014031 |
TP for 37.717-21-11 for DC_2-66_n7 |
Huawei,HiSilicon |
R4-2014032 |
TP for 37.717-21-11 for DC_2-5_n7 |
Huawei,HiSilicon |
R4-2014033 |
TP for 37.717-21-11 for DC_2-8_n2 |
Huawei,HiSilicon |
R4-2014034 |
TP for 37.717-21-11 for DC_5-66_n7 |
Huawei,HiSilicon |
R4-2014035 |
TP for 37.717-21-11 for DC_20-32_n1 |
Huawei,HiSilicon |
R4-2014036 |
TP for 37.717-21-11 for DC_20-32_n3 |
Huawei,HiSilicon |
R4-2014103 |
TP for TR 37.717-21-11 DC_1-3_n3 |
Samsung, KDDI |
R4-2014104 |
TP for TR 37.717-21-11 DC_1-41_n3 |
Samsung, KDDI |
R4-2014105 |
TP for TR 37.717-21-11 DC_3-18_n3 |
Samsung, KDDI |
R4-2014106 |
TP for TR 37.717-21-11 DC_3-41_n3 |
Samsung, KDDI |
R4-2014128 |
TP for TR 37.717-21-11 DC_5A-7A_n66A |
Samsung, TELUS, Bell mobility |
R4-2014129 |
TP for TR 37.717-21-11 DC_7-66_n77 |
Samsung, TELUS, Bell mobility |
R4-2014132 |
TP for TR 37.717-21-11 DC_2-5_n48 |
Samsung, Verizon |
R4-2014133 |
TP for TR 37.717-21-11 DC_2-13_n48 |
Samsung, Verizon |
R4-2014135 |
TP for TR 37.717-21-11 DC_2-48_n5 |
Samsung, Verizon |
R4-2014136 |
TP for TR 37.717-21-11 DC_5-46_n66 |
Samsung, Verizon |
R4-2014137 |
TP for TR 37.717-21-11 DC_5-66_n48 |
Samsung, Verizon |
R4-2014138 |
TP for TR 37.717-21-11 DC_5-66_n77 |
Samsung, Verizon |
R4-2014139 |
TP for TR 37.717-21-11 DC_13-48_n77 |
Samsung, Verizon |
R4-2014144 |
Draft CR for 38.101-3 to introduce new inter-band EN-DC (2LTE band+1NR band) within FR1 |
Samsung, SK Telecom, KT, KDDI, Verizon |
R4-2014612 |
TP for TR 37.717-21-11: EN-DC_1-42_n3 |
SoftBank Corp. |
R4-2014613 |
TP for TR 37.717-21-11: EN-DC_8-42_n3 |
SoftBank Corp. |
R4-2014614 |
TP update for TR 37.717-21-11: EN-DC_1-11_n28 |
SoftBank Corp., LG Electronics |
R4-2014811 |
TP for DC_3-18_n28 |
KDDI Corporation |
R4-2014831 |
Draft CR to 38.101-3: Error correction of EN-DC configurations |
Verizon Denmark |
R4-2014852 |
TP for TR 37.717-21-11: CA_2-66_n77 |
Verizon Denmark |
R4-2014854 |
TP for TR 37.717-21-11: CA_2-48_n77 |
Verizon Denmark |
R4-2014856 |
TP for TR 37.717-21-11: CA_2-13_n77 |
Verizon Denmark |
R4-2014857 |
TP for TR 37.717-21-11: CA_2-5_n77 |
Verizon Denmark |
R4-2014858 |
TP for TR 37.717-21-11: CA_5-13_n66 |
Verizon Denmark |
R4-2014860 |
TP for TR 37.717-21-11: CA_13-66_n77 |
Verizon Denmark |
R4-2014862 |
TP for TR 37.717-21-11: CA_13-66_n5 |
Verizon Denmark |
R4-2014864 |
TP for TR 37.717-21-11: CA_48-66_n77 |
Verizon Denmark |
R4-2014952 |
TP for DC_1-18_n28 |
KDDI Corporation |
R4-2014953 |
TP for DC_1-18_n41 |
KDDI Corporation |
R4-2014982 |
TP for DC_3-42_n1 for TR 37.717-21-11 |
NTT DOCOMO, INC. |
R4-2015072 |
draftCR for DC_1A-1A-3A_n28A, DC_1A-1A-3C_n28A, DC_1A-1A-3A_n78A, DC_1A-1A-3C_n78A, DC_1A-1A-5A_n78A, DC_1A-1A-7A_n28A, DC_1A-1A-28A_n78A, and DC_3C-5A_n78A |
Nokia, Nokia Shanghai Bell |
R4-2015225 |
TP for 37.717-21-11 to introduce DC_5A-7A_n7A |
Nokia |
R4-2015226 |
TP for 37.717-21-11 to introduce DC_2A-28A_n7A |
Nokia, ZTE |
R4-2015227 |
TP for 37.717-21-11 to introduce DC_28A-66A_n7A |
Nokia, ZTE |
R4-2015228 |
TP for 37.717-21-11 to introduce DC_7A-28A_n2A |
Nokia, ZTE |
R4-2015229 |
TP for 37.717-21-11 to introduce DC_2A-7A_n7A |
Nokia |
R4-2015246 |
TP for 37.717-21-11 to introduce DC_2A-71A_n71A and DC_66A-71A_n71A |
Nokia, T-Mobile |
R4-2015268 |
TP to TR 37.717-21-11 DC_1A-40C_n78A |
Huawei, HiSilicon, Ericsson |
R4-2015269 |
TP to TR 37.717-21-11 DC_3A-40C_n78A |
Huawei, HiSilicon, Ericsson |
R4-2015270 |
TP to TR 37.717-21-11 DC_7A-40C_n78A |
Huawei, HiSilicon, Ericsson |
R4-2015271 |
TP to TR 37.717-21-11 DC_8A-40C_n78A |
Huawei, HiSilicon |
R4-2015404 |
TP for TR 37.717-21-11: DC_7A-66A_n7A/DC_7A-66A-66A_n7A |
Huawei, HiSilicon |
R4-2015710 |
TP for TR 37.717-21-11: DC_2-7_n77 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2015711 |
TP for TR 37.717-21-11: DC_7-66_n77 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2015929 |
TP for TR 37.717-21-11 to include DC_1A-40A_n78A, DC_1A-40C_n78A |
Ericsson |
R4-2015930 |
TP for TR 37.717-21-11 to include DC_3A-40A_n78A, DC_3A-40C_n78A |
Ericsson |
R4-2015931 |
TP for TR 37.717-21-11 to include DC_7A-40A_n78A, DC_7A-40C_n78A |
Ericsson |
R4-2016310 |
CR to add CA_n7B UL configurations |
Ericsson, Telstra |
R4-2016656 |
TP for 37.717-21-11 for DC_20-32_n1 |
Huawei,HiSilicon |
R4-2016659 |
TP for TR 37.717-21-11 DC_13-48_n77 |
Samsung, Verizon |
R4-2016662 |
TP update for TR 37.717-21-11: EN-DC_1-11_n28 |
SoftBank Corp., LG Electronics |
R4-2016664 |
TP for DC_1-18_n28 |
KDDI Corporation |
R4-2016665 |
TP for DC_1-18_n41 |
KDDI Corporation |
R4-2016668 |
TP for 37.717-21-11 to introduce DC_5A-7A_n7A |
Nokia |
R4-2016669 |
TP for 37.717-21-11 to introduce DC_28A-66A_n7A |
Nokia, ZTE |
R4-2016671 |
TP for 37.717-21-11 to introduce DC_2A-71A_n71A and DC_66A-71A_n71A |
Nokia, T-Mobile |
R4-2016678 |
TP for TR 37.717-21-11: DC_7-66_n77 |
Huawei, HiSilicon, Bell Mobility, Telus |
10.4.3 |
DMEN-DC with FR2 band [DC_R17_2BLTE_1BNR_3DL2UL-Core] |
|
R4-2014134 |
TP for TR 37.717-21-11 DC_2-46_n261 |
Samsung, Verizon |
R4-2014140 |
TP for TR 37.717-21-11 DC_13-46_n261 |
Samsung, Verizon |
R4-2014143 |
Draft CR for 38.101-3 to introduce new inter-band EN-DC (2LTE band+1NR band) including FR2 |
Samsung, Verizon |
R4-2014609 |
Draft CR for TS 38.101-3: Support of Uplink n257D/G/H/I for DC_1-8_n257, DC_1-11_n257, DC_3-8_n257 and DC_8-11_n257 |
SoftBank Corp. |
R4-2015133 |
Draft CR for 38.101-3 to add UL EN-DC configurations including FR2 with 3DL and 2UL |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
R4-2015222 |
draftCR to introduce DC_3A-8A_n258 to 38.101-3 |
Nokia |
R4-2015223 |
draftCR to introduce DC_7A-8A_n258 to 38.101-3 |
Nokia |
R4-2015224 |
draftCR to introduce DC_3A-7A_n258 to 38.101-3 |
Nokia |
R4-2016660 |
TP for TR 37.717-21-11 DC_13-46_n261 |
Samsung, Verizon |
10.5 |
DC of 3 LTE band and 1 NR band [DC_R17_3BLTE_1BNR_4DL2UL] |
|
R4-2014059 |
TP for TR 37.717-31-11: DC_1-7-32_n78 |
VODAFONE Group Plc |
R4-2014060 |
TP for TR 37.717-31-11: DC_1-20-32_n28 |
VODAFONE Group Plc |
R4-2014061 |
TP for TR 37.717-31-11: DC_1-20-32_n78 |
VODAFONE Group Plc |
R4-2014062 |
TP for TR 37.717-31-11: DC_3-7-32_n78 |
VODAFONE Group Plc |
R4-2014063 |
TP for TR 37.717-31-11: DC_3-20-32_n78 |
VODAFONE Group Plc |
R4-2014064 |
TP for TR 37.717-31-11: DC_7-20-32_n1 |
VODAFONE Group Plc |
10.5.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_3BLTE_1BNR_4DL2UL-Core/Perf] |
|
R4-2015917 |
Revised WID LTE 3DL and one NR band Rel-17 |
Ericsson |
R4-2015921 |
CR introduction completed band combinations LTE 3DL and one NR band - |
Ericsson |
R4-2015925 |
TR 37.717-31-11 v0.2.0 Rel-17 DC combinations LTE 3DL and one NR band |
Ericsson |
10.5.2 |
EN-DC without FR2 band [DC_R17_3BLTE_1BNR_4DL2UL-Core] |
|
R4-2014037 |
TP for 37.717-31-11 for DC_1-20-32_n3 |
Huawei,HiSilicon |
R4-2014038 |
TP for 37.717-31-11 for DC_2-4-7_n28 |
Huawei,HiSilicon |
R4-2014039 |
TP for 37.717-31-11 for DC_2-5-7_n66 |
Huawei,HiSilicon |
R4-2014040 |
TP for 37.717-31-11 for DC_2-5-66_n7 |
Huawei,HiSilicon |
R4-2014041 |
TP for 37.717-31-11 for DC_2-5-66_n66 |
Huawei,HiSilicon |
R4-2014042 |
TP for 37.717-31-11 for DC_2-7-66_n28 |
Huawei,HiSilicon |
R4-2014043 |
TP for 37.717-31-11 for DC_3-20-32_n1 |
Huawei,HiSilicon |
R4-2014107 |
TP for TR 37.717-31-11 DC_1-3-18_n3 |
Samsung, KDDI |
R4-2014108 |
TP for TR 37.717-31-11 DC_1-3-41_n3 |
Samsung, KDDI |
R4-2014109 |
TP for TR 37.717-31-11 DC_1-3-41_n41 |
Samsung, KDDI |
R4-2014130 |
TP for TR 37.717-31-11 DC_2-5-7_n66 |
Samsung, TELUS, Bell mobility |
R4-2014145 |
Draft CR for 38.101-3 to introduce new inter-band EN-DC (3LTE band+1NR band) within FR1 |
Samsung, SK Telecom, KT, KDDI |
R4-2014615 |
TP for TR 37.717-31-11: EN-DC_1-3-11_n28 |
SoftBank Corp. |
R4-2014616 |
TP for TR 37.717-31-11: EN-DC_1-3-11_n77 |
SoftBank Corp. |
R4-2014617 |
TP for TR 37.717-31-11: EN-DC_3-8-11_n28 |
SoftBank Corp. |
R4-2014618 |
TP for TR 37.717-31-11: EN-DC_3-8-11_n77 |
SoftBank Corp. |
R4-2014619 |
TP for TR 37.717-31-11: EN-DC_1-8-11_n28 |
SoftBank Corp. |
R4-2014807 |
TP for TR 37.717-31-11: DC_1A-3A-18A_n28A |
KDDI Corporation |
R4-2014845 |
TP for TR 37.717-31-11: DC_1A-3A-18A_n41A |
KDDI Corporation |
R4-2015073 |
draftCR for DC_1A-3C-5A_n78A, DC_1A-1A-3A-5A_n78A, DC_1A-1A-3C-5A_n78A, DC_1A-1A-3A-7A_n78A, DC_1A-1A-3C-7A_n78A, DC_1A-1A-3C-7A_n28A, DC_1A-1A-3A-28A_n78A, DC_1A-1A-3C-28A_n78A and DC_3C-5A-7A_n78A |
Nokia, Nokia Shanghai Bell |
R4-2015231 |
TP for 37.717-31-11 to introduce DC_2A-7A-28A_n7A |
Nokia |
R4-2015247 |
TP for 37.717-31-11 to introduce DC_2A-66A-71A_n71A |
Nokia, T-Mobile |
R4-2015248 |
TP for 37.717-31-11 to introduce DC_2-5-66_n77A |
Nokia, Verizon |
R4-2015249 |
TP for 37.717-31-11 to introduce DC_2-13-66_n77A |
Nokia, Verizon |
R4-2015250 |
TP for 37.717-31-11 to introduce DC_2-48-66_n77A |
Nokia, Verizon |
R4-2015272 |
TP to TR 37.717-31-11 DC_1A-3A-40C_n78A |
Huawei, HiSilicon, Nokia, Ericsson |
R4-2015273 |
TP to TR 37.717-31-11 DC_1A-7A-40C_n78A |
Huawei, HiSilicon, Ericsson |
R4-2015274 |
TP to TR 37.717-31-11 DC_1A-8A-40C_n78A |
Huawei, HiSilicon, Nokia |
R4-2015275 |
TP to TR 37.717-31-11 DC_3A-7A-40C_n78A |
Huawei, HiSilicon, Ericsson |
R4-2015276 |
TP to TR 37.717-31-11 DC_3A-8A-40C_n78A |
Huawei, HiSilicon, Nokia |
R4-2015277 |
TP to TR 37.717-31-11 DC_7A-8A-40C_n78A |
Huawei, HiSilicon |
R4-2015405 |
TP for TR 37.717-31-11: DC_1A-7A-8A_n28A |
Huawei, HiSilicon |
R4-2015406 |
TP for TR 37.717-31-11: DC_3A-7A-8A_n28A |
Huawei, HiSilicon |
R4-2015407 |
TP for TR 37.717-31-11: DC_1A-7A-28A_n3A |
Huawei, HiSilicon |
R4-2015408 |
TP for TR 37.717-31-11: DC_3A-8A-40A_n1A/DC_3A-8A-40C_n1A |
Huawei, HiSilicon |
R4-2015409 |
TP for TR 37.717-31-11: DC_7A-8A-40A_n1A/DC_7A-8A-40C_n1A |
Huawei, HiSilicon |
R4-2015410 |
DraftCR for 38.101-3 to add configuration DC_3A-7A-40C_n1A |
Huawei, HiSilicon |
R4-2015411 |
TP for TR 37.717-31-11: DC_2A-28A-66A_n7A |
Huawei, HiSilicon |
R4-2015412 |
TP for TR 37.717-31-11: DC_2A-5A-7A_n7A |
Huawei, HiSilicon |
R4-2015413 |
TP for TR 37.717-31-11: DC_2A-7A-66A_n7A/DC_2A-7A-66A-66A_n7A |
Huawei, HiSilicon |
R4-2015414 |
TP for TR 37.717-31-11: DC_5A-7A-66A_n7A/DC_5A-7A-66A-66A_n7A |
Huawei, HiSilicon |
R4-2015415 |
TP for TR 37.717-31-11: DC_7A-28A-66A_n7A |
Huawei, HiSilicon |
R4-2015712 |
TP for TR 37.717-31-11: DC_2-7-66_n77 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2015932 |
TP for TR 37.717-31-11 to include DC_1A-3A-40A_n78A, DC_1A-3A-40C_n78A |
Ericsson |
R4-2015933 |
TP for TR 37.717-31-11 to include DC_1A-7A-40A_n78A, DC_1A-7A-40C_n78A |
Ericsson |
R4-2015934 |
TP for TR 37.717-31-11 to include DC_3A-7A-40A_n78A, DC_3A-7A-40C_n78A |
Ericsson |
R4-2015944 |
draft CR 38.101-3 to add DC_2A-2A-5A-66A_n66A |
Ericsson, Bell |
R4-2016311 |
CR to add CA_n7B UL configurations |
Ericsson, Telstra |
10.5.3 |
EN-DC with FR2 band [DC_R17_3BLTE_1BNR_4DL2UL-Core] |
|
R4-2014611 |
Draft CR for TS 38.101-3: Support of Uplink n257D/G/H/I for DC_1-3-8_n257 and DC_1A-8-11_n257 |
SoftBank Corp. |
R4-2015134 |
Draft CR for 38.101-3 to add EN-DC configurations including FR2 with 4DL and 2UL |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
R4-2015230 |
draftCR to introduce DC_3A-7A-8A_n258 to 38.101-3 |
Nokia |
10.6.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_4BLTE_1BNR_5DL2UL-Core/Perf] |
|
R4-2015214 |
Revised Rel-17 WID on DC of 4 bands LTE inter-band CA (4DL1UL) and 1 NR band (1DL1UL) |
Nokia, Nokia Shanghai Bell |
R4-2015215 |
CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 |
Nokia, Nokia Shanghai Bell |
R4-2015216 |
draftTR 37.717-41-11 v0.2.0 |
Nokia, Nokia Shanghai Bell |
10.6.2 |
EN-DC without FR2 band [DC_R17_4BLTE_1BNR_5DL2UL-Core] |
|
R4-2014044 |
TP for 37.717-41-11 for DC_2-5-7-66_n66 |
Huawei,HiSilicon |
R4-2014146 |
Draft CR for 38.101-3 to introduce new inter-band EN-DC (4LTE band+1NR band) within FR1 |
Samsung, SK Telecom |
R4-2015074 |
draft CR for DC_1A-1A-3A-5A-7A_n78A, DC_1A-3C-5A-7A_n78A, and DC_1A-1A-3A-7A-28A_n78A |
Nokia, Nokia Shanghai Bell |
R4-2015278 |
TP to TR 37.717-41-11 DC_1A-3A-7A-40C_n78A |
Huawei, HiSilicon |
R4-2015279 |
TP to TR 37.717-41-11 DC_1A-3A-8A-40C_n78A |
Huawei, HiSilicon, Nokia |
R4-2015280 |
TP to TR 37.717-41-11 DC_1A-7A-8A-40C_n78A |
Huawei, HiSilicon |
R4-2015281 |
TP to TR 37.717-41-11 DC_3A-7A-8A-40C_n78A |
Huawei, HiSilicon |
R4-2015416 |
TP for TR 37.717-41-11: DC_2A-7A-28A-66A_n7A |
Huawei, HiSilicon |
R4-2015417 |
TP for TR 37.717-41-11:DC_2A-5A-7A-66A_n7A/DC_2A-5A-7A-66A-66A_n7A |
Huawei, HiSilicon |
R4-2015418 |
TP for TR 37.717-41-11:DC_1A-3A-7A-8A_n28A |
Huawei, HiSilicon |
R4-2015419 |
TP for TR 37.717-41-11:DC_3A-7A-8A-40A_n1A/DC_3A-7A-8A-40C_n1A |
Huawei, HiSilicon |
R4-2015935 |
TP for TR 37.717-41-11 to include DC_1A-3A-7A-40A_n78A, DC_1A-3A-7A-40C_n78A |
Ericsson |
R4-2016657 |
TP for 37.717-41-11 for DC_2-5-7-66_n66 |
Huawei,HiSilicon |
R4-2016672 |
TP to TR 37.717-41-11 DC_1A-3A-7A-40C_n78A |
Huawei, HiSilicon |
R4-2016673 |
TP to TR 37.717-41-11 DC_1A-3A-8A-40C_n78A |
Huawei, HiSilicon, Nokia |
R4-2016674 |
TP to TR 37.717-41-11 DC_1A-7A-8A-40C_n78A |
Huawei, HiSilicon |
R4-2016675 |
TP to TR 37.717-41-11 DC_3A-7A-8A-40C_n78A |
Huawei, HiSilicon |
R4-2016677 |
TP for TR 37.717-41-11:DC_3A-7A-8A-40A_n1A/DC_3A-7A-8A-40C_n1A |
Huawei, HiSilicon |
10.6.3 |
EN-DC with FR2 band [DC_R17_4BLTE_1BNR_5DL2UL-Core] |
|
R4-2015135 |
Draft CR for 38.101-3 to add UL EN-DC configurations including FR2 with 5DL and 2UL |
SK Telecom, Samsung, Ericsson, Nokia, LGE |
10.7.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_xBLTE_2BNR_yDL2UL-Core/Per] |
|
R4-2014304 |
TR 37.717-11-21 v0.2.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics Polska |
R4-2014305 |
Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) EN DC in Rel-17 |
LG Electronics Polska |
R4-2014306 |
Introducing CR on new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics Polska |
10.7.2 |
EN-DC including NR inter CA without FR2 band [DC_R17_xBLTE_2BNR_yDL2UL-Core] |
|
R4-2014071 |
TP for TR 37.717-11-21 DC_1_n3-n41 |
Samsung, KDDI |
R4-2014072 |
TP for TR 37.717-11-21 DC_1_n3-n77 |
Samsung, KDDI |
R4-2014073 |
TP for TR 37.717-11-21 DC_1_n41-n77 |
Samsung, KDDI |
R4-2014074 |
TP for TR 37.717-11-21 DC_1-3_n3-n41 |
Samsung, KDDI |
R4-2014075 |
TP for TR 37.717-11-21 DC_1-3_n3-n77 |
Samsung, KDDI |
R4-2014076 |
TP for TR 37.717-11-21 DC_1-3_n3-n78 |
Samsung, KDDI |
R4-2014077 |
TP for TR 37.717-11-21 DC_1-3_n41-n77 |
Samsung, KDDI |
R4-2014078 |
TP for TR 37.717-11-21 DC_1-3-18_n3-n77 |
Samsung, KDDI |
R4-2014079 |
TP for TR 37.717-11-21 DC_1-3-18_n3-n78 |
Samsung, KDDI |
R4-2014080 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n41 |
Samsung, KDDI |
R4-2014081 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n77 |
Samsung, KDDI |
R4-2014082 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n78 |
Samsung, KDDI |
R4-2014083 |
TP for TR 37.717-11-21 DC_1-3-41_n41-n77 |
Samsung, KDDI |
R4-2014084 |
TP for TR 37.717-11-21 DC_1-3-41_n41-n78 |
Samsung, KDDI |
R4-2014085 |
TP for TR 37.717-11-21 DC_1-18_n3-n77 |
Samsung, KDDI |
R4-2014086 |
TP for TR 37.717-11-21 DC_1-41_n3-n41 |
Samsung, KDDI |
R4-2014087 |
TP for TR 37.717-11-21 DC_1-41_n3-n77 |
Samsung, KDDI |
R4-2014088 |
TP for TR 37.717-11-21 DC_1-41_n3-n78 |
Samsung, KDDI |
R4-2014089 |
TP for TR 37.717-11-21 DC_1-41_n41-n77 |
Samsung, KDDI |
R4-2014090 |
TP for TR 37.717-11-21 DC_1-41_n41-n78 |
Samsung, KDDI |
R4-2014091 |
TP for TR 37.717-11-21 DC_3_n3-n41 |
Samsung, KDDI |
R4-2014092 |
TP for TR 37.717-11-21 DC_3_n41-n77 |
Samsung, KDDI |
R4-2014093 |
TP for TR 37.717-11-21 DC_3-18_n3-n77 |
Samsung, KDDI |
R4-2014094 |
TP for TR 37.717-11-21 DC_3-18_n3-n78 |
Samsung, KDDI |
R4-2014095 |
TP for TR 37.717-11-21 DC_3-41_n3-n41 |
Samsung, KDDI |
R4-2014096 |
TP for TR 37.717-11-21 DC_3-41_n3-n77 |
Samsung, KDDI |
R4-2014097 |
TP for TR 37.717-11-21 DC_3-41_n3-n78 |
Samsung, KDDI |
R4-2014098 |
TP for TR 37.717-11-21 DC_3-41_n41-n77 |
Samsung, KDDI |
R4-2014099 |
TP for TR 37.717-11-21 DC_3-41_n41-n78 |
Samsung, KDDI |
R4-2014100 |
TP for TR 37.717-11-21 DC_41_n3-n41 |
Samsung, KDDI |
R4-2014101 |
TP for TR 37.717-11-21 DC_41_n41-n77 |
Samsung, KDDI |
R4-2014102 |
TP for TR 37.717-11-21 DC_41_n41-n78 |
Samsung, KDDI |
R4-2014121 |
TP for TR 37.717-11-21 DC_2_n7-n66 |
Samsung, TELUS, Bell mobility |
R4-2014122 |
TP for TR 37.717-11-21 DC_2_n38-n66 |
Samsung, TELUS, Bell mobility |
R4-2014123 |
TP for TR 37.717-11-21 DC_2_n66-n78 |
Samsung, TELUS, Bell mobility |
R4-2014124 |
TP for TR 37.717-11-21 DC_2-7_n38-n66 |
Samsung, TELUS, Bell mobility |
R4-2014125 |
TP for TR 37.717-11-21 DC_7-66_n38-n78 |
Samsung, TELUS, Bell mobility |
R4-2014126 |
TP for TR 37.717-11-21 DC_12_n7-n66 |
Samsung, TELUS, Bell mobility |
R4-2014127 |
TP for TR 37.717-11-21 DC_66_n38-n66 |
Samsung, TELUS, Bell mobility |
R4-2014187 |
Discussion of MSD for 3DL2UL DC_42_n1-n79 and DC_19_n1-n77 due to UL IMD issues |
MediaTek Inc. |
R4-2014315 |
TP on summary of self-interference analysis for new EN-DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2014316 |
MSD anlaysis results for new DC band combinations |
LG Electronics France |
R4-2014608 |
TP for DC_19_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC., MediaTek Inc. |
R4-2014610 |
TP for DC_19_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC., MediaTek Inc. |
R4-2014647 |
TP for TR 37.717-11-21: EN-DC_11_n3-n77 |
SoftBank Corp. |
R4-2014648 |
TP for TR 37.717-11-21: EN-DC_11_n28-n77 |
SoftBank Corp. |
R4-2014650 |
TP for TR 37.717-11-21: EN-DC_42_n3-n28 |
SoftBank Corp. |
R4-2014651 |
TP for TR 37.717-11-21: EN-DC_42_n3-n77 |
SoftBank Corp. |
R4-2014653 |
TP for TR 37.717-11-21: EN-DC_1-8_n3-n77 |
SoftBank Corp. |
R4-2014667 |
TP for TR 37.717-11-21: EN-DC_1-11_n3-n28 |
SoftBank Corp. |
R4-2014681 |
TP for TR 37.717-11-21: EN-DC_8-11_n3-n28 |
SoftBank Corp. |
R4-2014689 |
TP for TR 37.717-11-21: EN-DC_1-8-42_n28-n77 |
SoftBank Corp. |
R4-2014808 |
TP for TR 37.717-11-21: EN-DC_1-3-18_n28-n77 |
KDDI Corporation |
R4-2014809 |
TP for TR 37.717-11-21: EN-DC_1-3-18_n28-n78 |
KDDI Corporation |
R4-2014812 |
TP for TR 37.717-11-21: DC_41A_n28A-n41A |
KDDI Corporation |
R4-2014825 |
TP for TR 37.717-11-21: DC_1A-18A_n28A-n41A |
KDDI Corporation |
R4-2014828 |
TP for TR 37.717-11-21: DC_1A-18A_n28A-n77A |
KDDI Corporation |
R4-2014830 |
TP for TR 37.717-11-21: DC_1A-18A_n28A-n78A |
KDDI Corporation |
R4-2014833 |
TP for TR 37.717-11-21: DC_1A-18A_n3A-n41A |
KDDI Corporation |
R4-2014840 |
TP for TR 37.717-11-21: DC_1A-18A_n41A-n77A |
KDDI Corporation |
R4-2014841 |
TP for TR 37.717-11-21: DC_1A-18A_n41A-n78A |
KDDI Corporation |
R4-2014851 |
TP for TR 37.717-11-21: EN-DC_1-3-41_n28-n41 |
KDDI Corporation |
R4-2014853 |
TP for TR 37.717-11-21: DC_1A-41A_n28A-n41A |
KDDI Corporation |
R4-2014855 |
TP for TR 37.717-11-21: DC_3A-18A_n28A-n41A |
KDDI Corporation |
R4-2014859 |
TP for TR 37.717-11-21: DC_3A-18A_n28A-n77A |
KDDI Corporation |
R4-2014863 |
TP for TR 37.717-11-21: DC_3A-18A_n28A-n78A |
KDDI Corporation |
R4-2014878 |
TP for TR 37.717-11-21: DC_3A-18A_n3A-n41A |
KDDI Corporation |
R4-2014879 |
TP for TR 37.717-11-21: DC_3A-18A_n41A-n77A |
KDDI Corporation |
R4-2014881 |
TP for TR 37.717-11-21: DC_3A-18A_n41A-n78A |
KDDI Corporation |
R4-2014882 |
TP for TR 37.717-11-21: DC_3A-41A_n28A-n41A |
KDDI Corporation |
R4-2014884 |
TP for TR 37.717-11-21: DC_3A_n28A-n41A |
KDDI Corporation |
R4-2014927 |
TP for TR 37.717-11-21: DC_18A_n28A-n41A |
KDDI Corporation |
R4-2014929 |
TP for TR 37.717-11-21: DC_18A_n28A-n77A |
KDDI Corporation |
R4-2014930 |
TP for TR 37.717-11-21: DC_18A_n28A-n78A |
KDDI Corporation |
R4-2014931 |
TP for TR 37.717-11-21: DC_18A_n3A-n41A |
KDDI Corporation |
R4-2014950 |
TP for TR 37.717-11-21: DC_18A_n41A-n77A |
KDDI Corporation |
R4-2014951 |
TP for TR 37.717-11-21: DC_18A_n41A-n78A |
KDDI Corporation |
R4-2014983 |
TP for DC_19_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014984 |
TP for DC_21_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014985 |
TP for DC_21_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014986 |
TP for DC_21_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014987 |
TP for DC_42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014988 |
TP for DC_42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014989 |
TP for DC_3-19_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014990 |
TP for DC_3-19_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014991 |
TP for DC_3-19_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014992 |
TP for DC_3-21_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014993 |
TP for DC_3-21_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014994 |
TP for DC_3-21_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014995 |
TP for DC_3-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014996 |
TP for DC_3-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014997 |
TP for DC_3-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014998 |
TP for DC_19-21_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2014999 |
TP for DC_19-21_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015000 |
TP for DC_19-21_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015001 |
TP for DC_19-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015002 |
TP for DC_19-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015003 |
TP for DC_19-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015004 |
TP for DC_21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015005 |
TP for DC_21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015006 |
TP for DC_21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015007 |
TP for DC_3-19-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015008 |
TP for DC_3-19-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015009 |
TP for DC_3-19-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015010 |
TP for DC_3-21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015011 |
TP for DC_3-21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015012 |
TP for DC_3-21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015013 |
TP for DC_19-21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015014 |
TP for DC_19-21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015015 |
TP for DC_19-21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015259 |
TP for DC_42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2015420 |
DraftCR for 38.101-3 to add UL configuration DC_3C_n1A-n78A |
Huawei, HiSilicon |
R4-2015421 |
TP for TR 37.717-11-21:DC_3A-20A_n1A-n78A/DC_3C-20A_n1A-n78A |
Huawei, HiSilicon |
R4-2015422 |
TP for TR 37.717-11-21:DC_7A-20A_n1A-n78A |
Huawei, HiSilicon |
R4-2015423 |
DraftCR for 38.101-3 to add UL configuration DC_3C_n1A and DC_3C_n78A for DC_3C-7A_n1A-n78A |
Huawei, HiSilicon |
R4-2015424 |
TP for TR 37.717-11-21:DC_3A-7A-20A_n1A-n78A/DC_3C-7A-20A_n1A-n78A |
Huawei, HiSilicon |
R4-2015936 |
TP for TR 37.717-11-21 to include DC_28A_n1A-n78A |
Ericsson |
R4-2015937 |
TP for TR 37.717-11-21 to include DC_3A-7A_n40A-n78A |
Ericsson |
R4-2015938 |
TP for TR 37.717-11-21 to include DC_1A-7A_n40A-n78A |
Ericsson |
R4-2015939 |
TP for TR 37.717-11-21 to include DC_7A-28A_n40A-n78A |
Ericsson |
R4-2015940 |
TP for TR 37.717-11-21 to include DC_3A-7A-28A_n40A-n78A |
Ericsson |
R4-2015941 |
TP for TR 37.717-11-21 to include DC_1A-3A-7A_n40A-n78A |
Ericsson |
R4-2015942 |
TP for TR 37.717-11-21 to include DC_1A-7A-28A_n40A-n78A |
Ericsson |
R4-2015943 |
TP for TR 37.717-11-21 to include DC_1A-3A-7A-28A_n40A-n78A |
Ericsson |
R4-2016312 |
CR to add CA_n7B UL configurations |
Ericsson, Telstra |
R4-2016313 |
TP for TR 37.717-11-21 to include DC_2A_n5A-n77A |
Ericsson, Verizon, LG Electronics |
R4-2016314 |
TP for TR 37.717-11-21 to include DC_2A-13A_n66A-n77A |
Ericsson, Verizon |
R4-2016315 |
TP for TR 37.717-11-21 to include DC_2A_n66A-n77A, DC_2A-2A_n66A-n77A |
Ericsson, Verizon, LG Electronics |
R4-2016316 |
TP for TR 37.717-11-21 to include DC_2A-66A_n66A-n77A |
Ericsson, Verizon |
R4-2016317 |
TP for TR 37.717-11-21 to include DC_2A-66A_n5A-n77A |
Ericsson, Verizon |
R4-2016318 |
TP for TR 37.717-11-21 to include DC_13A_n2A-n77A |
Ericsson, Verizon, LG Electronics |
R4-2016319 |
TP for TR 37.717-11-21 to include DC_13A_n5A-n48A |
Ericsson, Verizon |
R4-2016320 |
TP for TR 37.717-11-21 to include DC_13A_n48A-n66A |
Ericsson, Verizon |
R4-2016321 |
TP for TR 37.717-11-21 to include DC_13A_n66A-n77A |
Ericsson, Verizon, LG Electronics |
R4-2016322 |
TP for TR 37.717-11-21 to include DC_13A-66A_n66A-n77A |
Ericsson, Verizon |
R4-2016323 |
TP for TR 37.717-11-21 to include DC_13A-66A_n2A-n77A |
Ericsson, Verizon |
R4-2016324 |
TP for TR 37.717-11-21 to include DC_13-66_n5-n48 |
Ericsson, Verizon |
R4-2016325 |
TP for TR 37.717-11-21 to include DC_66_n2-n77 |
Ericsson, Verizon |
R4-2016326 |
TP for TR 37.717-11-21 to include DC_66_n5-n48 |
Ericsson, Verizon |
R4-2016327 |
TP for TR 37.717-11-21 to include DC_66_n5-n77 |
Ericsson, Verizon, LG Electronics |
R4-2016328 |
TP for TR 37.717-11-21 to include DC_66_n66-n77 |
Ericsson, Verizon |
R4-2016694 |
TP for TR 37.717-11-21 DC_1-3_n3-n41 |
Samsung, KDDI |
R4-2016695 |
TP for TR 37.717-11-21 DC_1-3_n3-n77 |
Samsung, KDDI |
R4-2016696 |
TP for TR 37.717-11-21 DC_1-3_n3-n78 |
Samsung, KDDI |
R4-2016697 |
TP for TR 37.717-11-21 DC_1-3-18_n3-n77 |
Samsung, KDDI |
R4-2016698 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n41 |
Samsung, KDDI |
R4-2016699 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n77 |
Samsung, KDDI |
R4-2016700 |
TP for TR 37.717-11-21 DC_1-3-41_n3-n78 |
Samsung, KDDI |
R4-2016701 |
TP for TR 37.717-11-21 DC_1-3-41_n41-n77 |
Samsung, KDDI |
R4-2016702 |
TP for TR 37.717-11-21 DC_1-3-41_n41-n78 |
Samsung, KDDI |
R4-2016703 |
TP for TR 37.717-11-21 DC_1-41_n3-n41 |
Samsung, KDDI |
R4-2016704 |
TP for TR 37.717-11-21 DC_1-41_n41-n77 |
Samsung, KDDI |
R4-2016705 |
TP for TR 37.717-11-21 DC_1-41_n41-n78 |
Samsung, KDDI |
R4-2016706 |
TP for TR 37.717-11-21 DC_3_n3-n41 |
Samsung, KDDI |
R4-2016707 |
TP for TR 37.717-11-21 DC_3-18_n3-n77 |
Samsung, KDDI |
R4-2016708 |
TP for TR 37.717-11-21 DC_3-41_n3-n41 |
Samsung, KDDI |
R4-2016709 |
TP for TR 37.717-11-21 DC_3-41_n3-n77 |
Samsung, KDDI |
R4-2016710 |
TP for TR 37.717-11-21 DC_3-41_n3-n78 |
Samsung, KDDI |
R4-2016711 |
TP for TR 37.717-11-21 DC_3-41_n41-n77 |
Samsung, KDDI |
R4-2016712 |
TP for TR 37.717-11-21 DC_3-41_n41-n78 |
Samsung, KDDI |
R4-2016713 |
TP for TR 37.717-11-21 DC_41_n3-n41 |
Samsung, KDDI |
R4-2016714 |
TP for TR 37.717-11-21 DC_41_n41-n77 |
Samsung, KDDI |
R4-2016715 |
TP for TR 37.717-11-21 DC_41_n41-n78 |
Samsung, KDDI |
R4-2016716 |
TP for TR 37.717-11-21 DC_66_n38-n66 |
Samsung, TELUS, Bell mobility |
R4-2016717 |
TP for DC_19_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC., MediaTek Inc. |
R4-2016718 |
TP for DC_19_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC., MediaTek Inc. |
R4-2016719 |
TP for TR 37.717-11-21: EN-DC_11_n3-n77 |
SoftBank Corp. |
R4-2016720 |
TP for TR 37.717-11-21: DC_41A_n28A-n41A |
KDDI Corporation |
R4-2016721 |
TP for TR 37.717-11-21: EN-DC_1-3-41_n28-n41 |
KDDI Corporation |
R4-2016722 |
TP for TR 37.717-11-21: DC_1A-41A_n28A-n41A |
KDDI Corporation |
R4-2016723 |
TP for TR 37.717-11-21: DC_3A-18A_n3A-n41A |
KDDI Corporation |
R4-2016724 |
TP for TR 37.717-11-21: DC_3A-41A_n28A-n41A |
KDDI Corporation |
R4-2016725 |
TP for TR 37.717-11-21: DC_3A_n28A-n41A |
KDDI Corporation |
R4-2016726 |
TP for TR 37.717-11-21: DC_18A_n3A-n41A |
KDDI Corporation |
R4-2016727 |
TP for DC_42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016728 |
TP for DC_42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016729 |
TP for DC_3-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016730 |
TP for DC_3-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016731 |
TP for DC_3-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016732 |
TP for DC_19-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016733 |
TP for DC_19-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016734 |
TP for DC_19-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016735 |
TP for DC_21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016736 |
TP for DC_21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016737 |
TP for DC_21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016738 |
TP for DC_3-19-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016739 |
TP for DC_3-19-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016740 |
TP for DC_3-19-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016741 |
TP for DC_3-21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016742 |
TP for DC_3-21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016743 |
TP for DC_3-21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016744 |
TP for DC_19-21-42_n1-n77 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016745 |
TP for DC_19-21-42_n1-n78 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016746 |
TP for DC_19-21-42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
R4-2016747 |
TP for DC_42_n1-n79 for TR 37.717-11-21 |
NTT DOCOMO, INC. |
10.7.3 |
EN-DC including NR inter CA with FR2 band [DC_R17_xBLTE_2BNR_yDL2UL-Core] |
|
R4-2015047 |
TP for 37.717-11-21_ DC_40_n41-n258 |
ZTE Corporation |
R4-2015048 |
TP for 37.717-11-21_ DC_40_n79-n258 |
ZTE Corporation |
R4-2015049 |
TP for 37.717-11-21_ DC_41_n79-n258 |
ZTE Corporation |
R4-2015232 |
TP for 37.717-11-21 to introduce DC_8A_n78A-n258 |
Nokia |
R4-2015233 |
TP for 37.717-11-21 to introduce DC_8A_n40A-n258 |
Nokia |
R4-2015234 |
TP for 37.717-11-21 to introduce DC_1A-8A_n78A-n258 |
Nokia |
R4-2015235 |
TP for 37.717-11-21 to introduce DC_3A-8A_n78A-n258 |
Nokia |
R4-2015236 |
TP for 37.717-11-21 to introduce DC_7A-8A_n78A-n258 |
Nokia |
R4-2015237 |
TP for 37.717-11-21 to introduce DC_1A-8A_n40A-n258 |
Nokia |
R4-2015238 |
TP for 37.717-11-21 to introduce DC_3A-8A_n40A-n258 |
Nokia |
R4-2015239 |
TP for 37.717-11-21 to introduce DC_7A-8A_n40A-n258 |
Nokia |
R4-2015240 |
TP for 37.717-11-21 to introduce DC_3A-7A-8A_n78A-n258 |
Nokia |
R4-2015241 |
TP for 37.717-11-21 to introduce DC_3A-7A-8A_n40A-n258 |
Nokia |
R4-2016301 |
TP for TR 37.717-11-21 to include DC_7A_n78A-n258A to M, DC_7C_n78A-n258A to M |
Ericsson, Telstra |
R4-2016302 |
TP for TR 37.717-11-21 to include DC_3A_n78A-n258A to M |
Ericsson, Telstra |
R4-2016303 |
TP for TR 37.717-11-21 to include DC_28A_n78A-n258A to M |
Ericsson, Telstra |
10.8.1 |
Rapporteur Input (WID/TR/CR) [NR_SUL_combos_R17-Core/Per] |
|
R4-2014800 |
Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
R4-2014801 |
TR 37.717-00-00 v0.2.0 |
Huawei, HiSilicon |
R4-2014802 |
CR on Introduction of completed SUL band combinations into TS 38.101-1 |
Huawei, HiSilicon |
R4-2014803 |
CR on Introduction of completed SUL band combinations into TS 38.101-3 |
Huawei, HiSilicon |
10.8.2 |
UE RF [NR_SUL_combos_R17-Core] |
|
R4-2015535 |
DraftCR for 38.101-1 to add BCS1 for SUL_n78A-n80A |
Huawei, HiSilicon |
R4-2015536 |
DraftCR for 38.101-1 to add BCS1 for SUL_n78A-n83A |
Huawei, HiSilicon |
R4-2015537 |
DraftCR for 38.101-1 to add BCS1 for SUL_n78A-n84A |
Huawei, HiSilicon |
R4-2015538 |
DraftCR for 38.101-1 to add BCS1 for SUL_n41A-n80A |
Huawei, HiSilicon |
R4-2015539 |
DraftCR for 38.101-1 to add BCS1 for SUL_n79A-n80A |
Huawei, HiSilicon |
R4-2015540 |
TP for TR 37.717-00-00 to correct the notation of SUL band combinations |
Huawei, HiSilicon |
R4-2015541 |
TP for TR 37.717-00-00 for CA_n1A_SUL_n78A-n80A |
Huawei, HiSilicon |
R4-2015542 |
TP for TR 37.717-00-00 for CA_n1A_SUL_n78A-n84A |
Huawei, HiSilicon |
R4-2015543 |
TP for TR 37.717-00-00 for CA_n41A_SUL_n79A-n80A |
Huawei, HiSilicon |
R4-2015544 |
TP for TR 37.717-00-00 for CA_n79A_SUL_n41A-n80A |
Huawei, HiSilicon |
R4-2015545 |
DraftCR for 38.101-1 to add configuration for SUL_n41C-n80A / SUL_n41C-n83A / SUL_n78C-n80A / SUL_n78C-n84A / SUL_n79C-n80A / SUL_n79C-n83A |
Huawei, HiSilicon |
R4-2016748 |
TP for TR 37.717-00-00 for CA_n1A_SUL_n78A-n80A |
Huawei, HiSilicon |
R4-2016749 |
TP for TR 37.717-00-00 for CA_n1A_SUL_n78A-n84A |
Huawei, HiSilicon |
R4-2016750 |
TP for TR 37.717-00-00 for CA_n41A_SUL_n79A-n80A |
Huawei, HiSilicon |
R4-2016751 |
TP for TR 37.717-00-00 for CA_n79A_SUL_n41A-n80A |
Huawei, HiSilicon |
10.9.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R17_3BDL_1BUL-Core/Per] |
|
R4-2014460 |
TR 38.717-03-01 on Rel-17 NR inter-band Carrier Aggregation (CA) for 3 Down Link (DL) / 1 Up Link (UL) |
CATT |
R4-2014461 |
Revised WID on Rel-17 NR inter-band CA of 3DL bands and 1UL band |
CATT |
10.9.2 |
UE RF [NR_CA_R17_3BDL_1BUL-Core] |
|
R4-2014112 |
TP for TR 38.717-03-01 CA_n3-n41-n77 |
Samsung, KDDI |
R4-2014113 |
TP for TR 38.717-03-01 CA_n3-n41-n78 |
Samsung, KDDI |
R4-2014114 |
TP for TR 38.717-03-01 CA_n28-n41-n77 |
Samsung, KDDI |
R4-2014115 |
TP for TR 38.717-03-01 CA_n28-n41-n78 |
Samsung, KDDI |
R4-2014462 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 |
CATT |
R4-2014463 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 |
CATT |
R4-2014523 |
draft CR for NR inter-band CA for 3 bands DL |
Nokia, T-Mobile USA |
R4-2014526 |
TP for TR 38.717-03-01: CA_n1A-n8A-n78(2A) |
Nokia, Telefonica |
R4-2015051 |
TP for TR38.717-03-01_ CA_n8A-n40A-n41A |
ZTE Corporation |
R4-2015078 |
TP to TR 38.717-03-01: CA_n5-n66-n77 |
Nokia, Nokia Shanghai Bell |
R4-2015079 |
TP to TR 38.717-03-01: CA_n2-n66-n77 |
Nokia, Nokia Shanghai Bell |
R4-2015242 |
draftCR to introduce CA_n1A-n40A-n258 to 38.101-3 |
Nokia |
R4-2015243 |
draftCR to introduce CA_n1A-n78A-n258 to 38.101-3 |
Nokia |
R4-2015244 |
draftCR to introduce CA_n40A-n78A-n258 to 38.101-3 |
Nokia |
R4-2015707 |
TP for TR 38.717-03-01: CA_n66-n71-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2015708 |
TP for TR 38.717-03-01: CA_n38-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2015709 |
TP for TR 38.717-03-01: CA_n25-n38-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2016305 |
TP to add CA_n3A-n5A-n7A, CA_n3A-n5A-n7B |
Ericsson, Telstra |
R4-2016306 |
TP to add CA_n5A-n7A-n78A, CA_n5A-n7B-n78A |
Ericsson, Telstra |
R4-2016649 |
TP to add 3DL/1UL CA_n25A-n41A-n77A, CA_n25A-n41(2A)-n77A, CA_n25A-n41C-n77A |
Ericsson, T-Mobile US |
R4-2016650 |
TP to add 3DL/1UL CA_n25A-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016651 |
TP to add 3DL/1UL CA_n25A-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016652 |
TP to add 3DL/1UL CA_n41A-n66A-n77A, CA_n41(2A)-n66A-n77A, CA_n41C-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016653 |
TP to add 3DL/1UL CA_n41A-n71A-n77A, CA_n41(2A)-n71A-n77A, CA_n41C-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016654 |
TP to add 3DL/1UL CA_n66A-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016752 |
TP for TR 38.717-03-01 CA_n3-n41-n77 |
Samsung, KDDI |
R4-2016753 |
TP for TR 38.717-03-01 CA_n3-n41-n78 |
Samsung, KDDI |
R4-2016754 |
TP for TR 38.717-03-01: CA_n1A-n8A-n78(2A) |
Nokia, Telefonica |
10.10.1 |
Rapporteur Input (WID/TR/CR) [NR_CA_R17_4BDL_1BUL-Core/Per] |
|
R4-2015918 |
Revised WID 4 bands NR CA Rel-17 |
Ericsson |
R4-2015922 |
CR introduction completed band combinations NR Inter-band 4 bands CA - |
Ericsson |
R4-2015923 |
CR introduction completed band combinations NR Inter-band 4 bands CA - |
Ericsson |
R4-2015926 |
TR 38.717-04-01 v0.2.0 Rel-17 NR Inter-band 4 bands CA |
Ericsson |
10.10.2 |
UE RF [NR_CA_R17_4BDL_1BUL-Core] |
|
R4-2014118 |
TP for TR 38.717-04-01 CA_n3-n28-n41-n77 |
Samsung, KDDI |
R4-2014816 |
TP for CA_n1-n77-n79-n257 4DL/1UL for TR38.717-04-01 |
NTT DOCOMO, INC. |
R4-2014817 |
TP for CA_n1-n78-n79-n257 4DL/1UL for TR38.717-04-01 |
NTT DOCOMO, INC. |
R4-2016307 |
TP to add CA_n3A-n5A-n7A-n78A, CA_n3A-n5A-n7B-n78A |
Ericsson, Telstra |
10.11.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R17_3BDL_2BUL-Core/Per] |
|
R4-2015060 |
Revised WID on Rel-17 NR Inter-band Carrier AggregationDual Connectivity for 3 bands DL with 2 bands UL |
ZTE Corporation |
R4-2015061 |
Draft CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2015062 |
Draft CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2015185 |
TR 38.717-03-02 v0.2.0 |
ZTE Wistron Telecom AB |
R4-2017807 |
CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-1 |
ZTE |
R4-2017808 |
CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-3 |
ZTE |
10.11.2 |
UE RF [NR_CADC_R17_3BDL_2BUL-Core] |
|
R4-2014116 |
TP for TR 38.717-03-02 CA_n3-n28-n41 |
Samsung, KDDI |
R4-2014117 |
TP for TR 38.717-03-02 CA_n3-n28-n78 |
Samsung, KDDI |
R4-2014595 |
TP for CA 3DL2UL n1-n77-n79 for TR 38.717-03-02 |
NTT DOCOMO, INC., MediaTek Inc., LG Electronics |
R4-2014599 |
TP for CA 3DL2UL n1-n78-n79 for TR 38.717-03-02 |
NTT DOCOMO, INC., MediaTek Inc., LG Electronics |
R4-2014814 |
draft CR 38.101-3 to add DC_n1-n77-n257, DC_n1-n78-n257, DC_n1-n79-n257, DC_n77-n79-n257 and DC_n78-n79-n257 |
NTT DOCOMO, INC. |
R4-2015052 |
TP for TR38.717-03-02_ CA_n8A-n40A-n41A |
ZTE Corporation |
R4-2015068 |
MSD evaluation for CA 3DL2UL n1-n77-n79 for TR 38.717-03-02 |
MediaTek Inc. |
R4-2015080 |
TP to TR 38.717-03-02: CA_n5-n66-n77 |
Nokia, Nokia Shanghai Bell |
R4-2015081 |
TP to TR 38.717-03-02: CA_n2-n66-n77 |
Nokia, Nokia Shanghai Bell |
R4-2016333 |
TP to add CA_n25A-n41A-n77A, CA_n25A-n41(2A)-n77A, CA_n25A-n41C-n77A |
Ericsson, T-Mobile US |
R4-2016334 |
TP to add CA_n25A-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016335 |
TP to add CA_n25A-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016336 |
TP to add CA_n41A-n66A-n77A, CA_n41(2A)-n66A-n77A, CA_n41C-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016337 |
TP to add CA_n41A-n71A-n77A, CA_n41(2A)-n71A-n77A, CA_n41C-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016338 |
TP to add CA_n66A-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016755 |
TP for TR 38.717-03-02 CA_n3-n28-n41 |
Samsung, KDDI |
R4-2016756 |
TP for TR 38.717-03-02 CA_n3-n28-n78 |
Samsung, KDDI |
R4-2016757 |
TP for CA 3DL2UL n1-n77-n79 for TR 38.717-03-02 |
NTT DOCOMO, INC., MediaTek Inc., LG Electronics |
R4-2016758 |
TP for CA 3DL2UL n1-n78-n79 for TR 38.717-03-02 |
NTT DOCOMO, INC., MediaTek Inc., LG Electronics |
R4-2016759 |
TP to add CA_n25A-n41A-n77A, CA_n25A-n41(2A)-n77A, CA_n25A-n41C-n77A |
Ericsson, T-Mobile US |
R4-2016760 |
TP to add CA_n25A-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016761 |
TP to add CA_n25A-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016762 |
TP to add CA_n41A-n66A-n77A, CA_n41(2A)-n66A-n77A, CA_n41C-n66A-n77A |
Ericsson, T-Mobile US |
R4-2016763 |
TP to add CA_n41A-n71A-n77A, CA_n41(2A)-n71A-n77A, CA_n41C-n71A-n77A |
Ericsson, T-Mobile US |
R4-2016764 |
TP to add CA_n66A-n71A-n77A |
Ericsson, T-Mobile US |
10.12.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_xBLTE_yBNR_3DL3UL-Core/Per] |
|
R4-2015063 |
Revised WID on Rel-17 Dual Connectivity (DC) x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA |
ZTE Corporation |
R4-2015064 |
Draft CR to reflect the completed DC combinations for 3 bands DL with 3 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2015065 |
TR 37.717-33 v0.2.0 |
ZTE Corporation |
R4-2017809 |
CR to reflect the completed DC combinations for 3 bands DL with 3 bands UL into TS 38.101-3 |
ZTE |
10.13.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_xBLTE_3BNR_yDL2UL -Core/Per] |
|
R4-2015066 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE Corporation |
R4-2015067 |
TR 37.717-11-31_v0.2.0 |
ZTE Corporation |
R4-2015588 |
Draft CR to reflect the completed Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE Corporation |
R4-2017810 |
CR to reflect the completed Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE |
10.13.2 |
UE RF [DC_R17_xBLTE_3BNR_yDL2UL-Core] |
|
R4-2014706 |
TP for TR 37.716-11-31: EN-DC_1_n3-n28-n77 |
SoftBank Corp. |
R4-2014707 |
TP for TR 37.717-11-31: EN-DC_8_n3-n28-n77 |
SoftBank Corp. |
R4-2015050 |
TP for 37.717-11-31_ DC_8A_n40A-n41A-n79A |
ZTE Corporation |
R4-2015802 |
TP for TR 37.717-11-31: support of DC_3_n1-n78-n257, DC_3-3_n1-n78-n257, DC_7_n1-n78-n257, DC_7-7_n1-n78-n257 |
CHTTL |
R4-2015806 |
TP for TR 37.717-11-31: support of DC_3-7_n1-n78-n257, DC_3-3-7_n1-n78-n257, DC_3-7-7_n1-n78-n257, DC_3-3-7-7_n1-n78-n257 |
CHTTL |
R4-2016765 |
TP for TR 37.716-11-31: EN-DC_1_n3-n28-n77 |
SoftBank Corp. |
R4-2016766 |
TP for TR 37.717-11-31: EN-DC_8_n3-n28-n77 |
SoftBank Corp. |
10.14.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R17_4BDL_2BUL -Core/Per] |
|
R4-2014380 |
TR38.717-04-02 update version 0.2.0 |
Samsung Electronics GmbH |
R4-2014753 |
Revised WID on NR CA/DC with 4DL/2UL |
Samsung |
R4-2014754 |
CR on introduction of completed NR CA/DC combs with 4DL/2UL within FR1 |
Samsung |
R4-2014755 |
CR on introduction of completed NR CA/DC combs with 4DL/2UL including FR2 |
Samsung |
10.14.2 |
UE RF [NR_CADC_R17_4BDL_2BUL -Core] |
|
R4-2014119 |
TP for TR 38.717-04-02 CA_n3-n28-n41-n77 |
Samsung, KDDI |
R4-2014120 |
TP for TR 38.717-04-02 CA_n3-n28-n41-n78 |
Samsung, KDDI |
R4-2014815 |
draft CR 38.101-3 to add DC_n1-n77-n79-n257 and DC_n1-n78-n79-n257 |
NTT DOCOMO, INC. |
R4-2014818 |
TP for CA_n1-n77-n79-n257 4DL/2UL for TR38.717-04-02 |
NTT DOCOMO, INC. |
R4-2014819 |
TP for CA_n1-n78-n79-n257 4DL/2UL for TR38.717-04-02 |
NTT DOCOMO, INC. |
10.15.1 |
Rapporteur Input (WID/TR/CR) [NR_CADC_R17_5BDL_xBUL -Core/Per] |
|
R4-2014804 |
Revised WID on NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) |
Huawei, HiSilicon |
R4-2014805 |
TR 38.717-05-01 v0.2.0 |
Huawei, HiSilicon |
R4-2014806 |
CR on Introduction of completed 5 bands inter-band CA into TS 38.101-1 |
Huawei, HiSilicon |
10.16.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_5BLTE_1BNR_6DL2UL-Core/Per] |
|
R4-2014781 |
Revised WID on Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) |
Samsung |
R4-2014782 |
CR introduction completed band combinations for Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) |
Samsung |
R4-2014967 |
Skeleton on TR 37.717-51-11_0.0.1 |
Samsung |
R4-2014968 |
TR 37.717-51-11_0.1.0 |
Samsung |
10.16.2 |
UE RF [DC_R17_5BLTE_1BNR_6DL2UL-Core] |
|
R4-2015282 |
TP to TR 37.717-51-11 DC_1A-3A-7A-8A-40C_n78A |
Huawei, HiSilicon |
10.17.1 |
Rapporteur Input (WID/TR/CR) [DC_R17_xBLTE_2BNR_yDL3UL-Core/Per] |
|
R4-2014783 |
CR introduction completed band combinations for Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) |
Samsung |
R4-2014784 |
Revised WID on Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) |
Samsung |
R4-2014969 |
Skeleton on TR 37.717-21-22_0.0.1 |
Samsung |
R4-2014970 |
TR 37.717-21-22_0.1.0 |
Samsung |
10.17.2 |
UE RF [DC_R17_xBLTE_2BNR_yDL3UL-Core] |
|
R4-2015136 |
TP for TR 37.717-21-22: DC_1-3_n78-n257 |
SK Telecom, Samsung |
R4-2015137 |
TP for TR 37.717-21-22: DC_1-5_n78-n257 |
SK Telecom, Samsung |
R4-2015138 |
TP for TR 37.717-21-22: DC_1-7_n78-n257 and DC_1-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015139 |
TP for TR 37.717-21-22: DC_3-5_n78-n257 |
SK Telecom, Samsung |
R4-2015140 |
TP for TR 37.717-21-22: DC_3-7_n78-n257 and DC_3-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015141 |
TP for TR 37.717-21-22: DC_5-7_n78-n257 and DC_5-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015142 |
TP for TR 37.717-21-22: DC_1-3-5_n78-n257 |
SK Telecom, Samsung |
R4-2015143 |
TP for TR 37.717-21-22: DC_1-3-7_n78-n257 and DC_1-3-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015144 |
TP for TR 37.717-21-22: DC_1-5-7_n78-n257 and DC_1-5-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015145 |
TP for TR 37.717-21-22: DC_3-5-7_n78-n257 and DC_3-5-7-7_n78-n257 |
SK Telecom, Samsung |
R4-2015146 |
TP for TR 37.717-21-22: DC_1-3-5-7_n78-n257 and DC_1-3-5-7-7_n78-n257 |
SK Telecom, Samsung |
10.18 |
SAR schemes for UE power class 2 (PC2) for NR inter-band Carrier Aggregation and supplemental uplink (SUL) configurations with 2 bands UL [NR_SAR_PC2_interB_SUL_2BUL] |
|
R4-2016623 |
Email discussion summary for [97e][121] NR_SAR_PC2_interB_SUL_2BUL |
Moderator (China Telecom) |
R4-2016851 |
WF on SAR solutions for PC2 NR inter-band CA and SUL configurations |
China Telecom |
R4-2016852 |
WF on power configuration for PC2 NR inter-band CA |
Qualcomm |
R4-2016963 |
Email discussion summary for [97e][121] NR_SAR_PC2_interB_SUL_2BUL |
Moderator (China Telecom) |
10.18.1 |
General and Rapporteur Input (WID/TR/CR) [NR_SAR_PC2_interB_SUL_2BUL-Core/Per] |
|
R4-2014383 |
Discussion on SAR issues for inter-band and SUL 2UL CA PC2 |
CATT |
R4-2015039 |
On MSD for PC2 n41-n79 NR inter-band CA |
ZTE Corporation |
R4-2015266 |
MSD analysis on high power UE for CA_n41-n79 |
Xiaomi |
10.18.2 |
PC2 for inter-band CA [NR_SAR_PC2_interB_SUL_2BUL-Core] |
|
R4-2015040 |
Discussion on SAR solution for NR PC2 inter-band CA |
ZTE Corporation |
R4-2015190 |
Discussion on SAR schemes for UE power class 2 NR inter-band CA with 2UL |
China Telecom |
R4-2015192 |
draft CR to 38.101-1 Introduce SAR solution for UE power class 2 NR inter-band CA with 2UL |
China Telecom |
R4-2015193 |
draft CR to 38.101-1 Introduce band combination requirements for PC2 CA_n1A-n78A |
China Telecom |
R4-2015260 |
Discussion on SAR issue for HP UE inter-band UL CA |
Xiaomi |
R4-2015287 |
Discussion on the SAR solutions for UL CA band combinations |
Huawei, HiSilicon |
R4-2015329 |
Discussion on SAR solution for PC2 inter-band NR CA |
vivo |
R4-2015346 |
Discussion on inter-band CA HPUE SAR |
OPPO |
R4-2015889 |
CR to 38.101-1 Introduce band combination requirements for PC2 CA_n1A-n78A |
China Telecom, ZTE, Huawei, HiSilicon, CATT |
R4-2015983 |
Facilitating SAR compliance for UL inter-band CA PC2 |
Ericsson |
R4-2016439 |
Upper limits on output power for dual PA |
Qualcomm Incorporated |
10.18.3 |
PC2 for SUL [NR_SAR_PC2_interB_SUL_2BUL-Core] |
|
R4-2015041 |
Discussion on SAR solution for NR PC2 SUL |
ZTE Corporation |
R4-2015191 |
Discussion on SAR schemes for UE power class 2 NR SUL configurations |
China Telecom |
R4-2015194 |
draft CR to 38.101-1 Introduce SAR solution for UE power class 2 NR SUL configurations |
China Telecom |
R4-2015286 |
Discussion on the SAR solutions for SUL band combinations |
Huawei, HiSilicon |
R4-2015330 |
Discussion on SAR solution for PC2 UE with SUL |
vivo |
R4-2015345 |
Discussion on SUL HPUE SAR |
OPPO |
10.19 |
High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink [NR_PC2_CA_R17_2BDL_2BUL] |
|
R4-2016624 |
Email discussion summary for [97e][122] NR_PC2_CA_R17_2BDL_2BUL |
Moderator (China Telecom) |
R4-2016854 |
WF on MSD assumptions improvement for UE PC2 combinations |
China Telecom |
R4-2016964 |
Email discussion summary for [97e][122] NR_PC2_CA_R17_2BDL_2BUL |
Moderator (China Telecom) |
10.19.1 |
Rapporteur Input (WID/TR/CR) [NR_PC2_CA_R17_2BDL_2BUL-Core/Per] |
|
R4-2015186 |
Work plan and procedure for basket WI on high power UE for NR inter-band CA with 2 bands DL and 2 bands UL |
China Telecom |
R4-2015187 |
TR skeleton for TR 38.xxx 0.0.1: High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
China Telecom |
R4-2015188 |
Draft TR 38.xxx v0.1.0: High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
China Telecom |
R4-2015189 |
Revised WID: High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
China Telecom |
R4-2016853 |
Revised WID: High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
China Telecom |
10.19.2 |
UE RF [NR_PC2_CA_R17_2BDL_2BUL-Core] |
|
R4-2015053 |
TP for TR38.xxx_ PC2 CA_n3A-n41A |
ZTE Corporation, CMCC |
R4-2015054 |
TP for TR38.xxx_ PC2 CA_n28A-n41A |
ZTE Corporation, CMCC |
R4-2015055 |
TP for TR38.xxx_ PC2 CA_n28A-n79A |
ZTE Corporation, CMCC |
R4-2015056 |
TP for TR38.xxx_ PC2 CA_n40A-n41A |
ZTE Corporation, CMCC |
R4-2016441 |
MSD for Band n77 PC2 combinations |
Qualcomm Incorporated |
R4-2016855 |
TP for TR38.xxx_ PC2 CA_n3A-n41A |
ZTE Corporation, CMCC |
10.20 |
High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band [ENDC_UE_PC2_R17_NR_TDD] |
|
R4-2016625 |
Email discussion summary for [97e][123] ENDC_UE_PC2_R17_NR_TDD |
Moderator (China Unicom) |
R4-2016965 |
Email discussion summary for [97e][123] ENDC_UE_PC2_R17_NR_TDD |
Moderator (China Unicom) |
10.20.1 |
Rapporteur Input (WID/TR/CR) [ENDC_UE_PC2_R17_NR_TDD -Core/Per] |
|
R4-2014649 |
TR Skeleton for TR 37.826 v0.0.1 ENDC_UE_PC2_R17_NR_TDD |
China Unicom |
R4-2014708 |
Big CR on introduction of completed PC2 for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2014709 |
Big CR on introduction of completed PC2 for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2017840 |
TR Skeleton for TR 37.826 v0.1.0 ENDC_UE_PC2_R17_NR_TDD |
China Unicom |
R4-2017841 |
Revised WID on High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
10.20.2 |
UE RF [ENDC_UE_PC2_R17_NR_TDD -Core] |
|
R4-2014679 |
TP for TR 37.826 to introduce PC2 for DC_1A_n78A |
China Unicom |
R4-2014680 |
TP for TR 37.826 to introduce PC2 for DC_8A_n78A |
China Unicom |
R4-2015793 |
Discussion on release independent of FDD-TDD EN-DC High Power UE |
CHTTL |
R4-2016440 |
Improving PC2 MSD for EN-DC and UL CA |
Qualcomm Incorporated |
R4-2016856 |
TP for TR 37.826 to introduce PC2 for DC_1A_n78A |
China Unicom |
R4-2016857 |
TP for TR 37.826 to introduce PC2 for DC_8A_n78A |
China Unicom |
R4-2016987 |
CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE |
CHTTL, China Unicom |
10.21 |
Adding channel bandwidth support to existing NR bands [NR_bands_R17_BWs] |
|
R4-2016626 |
Email discussion summary for [97e][124] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2016966 |
Email discussion summary for [97e][124] NR_bands_R17_BWs |
Moderator (Ericsson) |
10.21.1 |
General and Rapporteur Input (WID/TR/CR) [NR_bands_R17_BWs -Core/Per] |
|
R4-2015910 |
Revised RP-201294 - Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
R4-2015911 |
Big CR to 38.104 - Additional Channel BW |
Ericsson |
R4-2015912 |
Big CR to 38.101-1 - Additional Channel BW |
Ericsson |
R4-2016858 |
Revised RP-201294 - Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
R4-2016859 |
Big CR to 38.104 - Additional Channel BW |
Ericsson |
R4-2016860 |
Big CR to 38.101-1 - Additional Channel BW |
Ericsson |
10.21.2 |
UE RF requirement [NR_bands_R17_BWs -Core] |
|
R4-2015292 |
Adding 40M bandwidth for band n80 and n83 |
Huawei, HiSilicon |
R4-2015293 |
draftCR to 38101-1 to add 40MHz BW for band n80 |
Huawei, HiSilicon |
R4-2015296 |
Adding 90 and 100MHz UE bandwidth for band n40 |
Huawei, HiSilicon |
R4-2015297 |
draftCR to 38101-1 to add 90 and 100MHz BW for band n40 |
Huawei, HiSilicon |
R4-2016861 |
draftCR to 38101-1 to add 90 and 100MHz BW for band n40 |
Huawei, HiSilicon |
10.21.2.2 |
MPR/A-MPR/NS signaling [NR_bands_R17_BWs -Core] |
|
R4-2014593 |
n40 MPR and Interference for Additional Channel Bandwidths |
Skyworks Solutions Inc. |
10.21.3 |
BS RF requirement [NR_bands_R17_BWs -Core] |
|
R4-2015294 |
draftCR to 38104 to add 40MHz BW for band n80 |
Huawei, HiSilicon |
R4-2015295 |
draftCR to 38104 to add 40MHz BW for band n83 |
Huawei, HiSilicon |
R4-2015298 |
draftCR to 38104 to add 90MHz BW for band n40 |
Huawei, HiSilicon |
10.22 |
Introduction of channel bandwidths 35MHz and 45MHz for NR [NR_FR1_35MHz_45MHz_BW] |
|
R4-2016452 |
35 and 45 MHz CH BW Release Independence |
T-Mobile USA, TELUS, Bell Mobility, AT&T |
R4-2016627 |
Email discussion summary for [97e][125] NR_FR1_35MHz_45MHz_BW |
Moderator (Huawei) |
R4-2016862 |
WF on release independence for 35 MHz and 45 MHz |
T-Mobile USA |
R4-2016863 |
WF on general aspects for UE RF requirements |
Skyworks |
R4-2016864 |
WF on UE REFSENS and A-MPR for 35MHz and 45MHz CBW |
Qualcomm |
R4-2016865 |
WF on BS RF requirements |
ZTE |
R4-2016967 |
Email discussion summary for [97e][125] NR_FR1_35MHz_45MHz_BW |
Moderator (Huawei) |
R4-2017814 |
LS to RAN2 on 35 and 45 MHz channel bandwidths |
T-Mobile USA |
R4-2017846 |
LS to RAN2 on 35 and 45 MHz channel bandwidths |
RAN4 |
10.22.1 |
General and Rapporteur Input (WID/TR/CR) [NR_FR1_35MHz_45MHz_BW-Core/Per] |
|
R4-2015701 |
Discussion on release independence |
Huawei, HiSilicon |
R4-2016113 |
Discussion on release independent and signalling for brand new channel bandwidth |
ZTE Corporation |
10.22.2 |
Spectrum utilization [NR_FR1_35MHz_45MHz_BW-Core] |
|
R4-2015043 |
Further discussion on spectrum utilization for 35MHz and 45MHz |
ZTE Corporation |
10.22.3 |
UE RF requirements [NR_FR1_35MHz_45MHz_BW-Core] |
|
R4-2014173 |
35M_45M AMPR, MPR, REFSENS |
Qualcomm Incorporated |
R4-2014186 |
REFSENS of n8 and n71 for new channel bandwidth |
MediaTek Inc. |
R4-2015044 |
On UE RF requirement for new channel bandwidth of 35MHz and 45MHz |
ZTE Corporation |
R4-2015351 |
Release independence for 35MHz and 45Mhz BW |
OPPO |
R4-2015432 |
REFSENS of n3, n8, n25 and n71 for new channel bandwidth |
Murata Manufacturing Co Ltd. |
R4-2015702 |
Draft CR for TS 38.101: introduction of channel bandwidths 35MHz and 45MHz for general part |
Huawei, HiSilicon |
R4-2015800 |
Specification impact of additional 35 |
Skyworks Solutions Inc. |
R4-2015801 |
Specification impact of additional 35&45MHz channel bandwidths |
Skyworks Solutions Inc. |
R4-2016010 |
n71 35MHz AMPR and MSD Measurements |
Skyworks Solutions Inc. |
R4-2016011 |
n8 35MHz AMPR and MSD Measurements |
Skyworks Solutions Inc. |
R4-2016027 |
n7 35MHz AMPR and MSD Measurements |
Skyworks Solutions Inc. |
R4-2016059 |
Draft CR to add 35MHz and 45 MHz Bandwidth to TS38.101-1 |
Ericsson |
R4-2016060 |
Introduction of 35MHz and 45MHz regarding CA, DC, V2x combinations |
Ericsson |
R4-2016295 |
Introduction of 35 MHz for n8, n66, n71 and 45 MHz for n66 |
Apple Inc. |
R4-2016600 |
35M_45M AMPR, MPR, REFSENS |
Qualcomm Incorporated |
10.22.4 |
BS RF requirements [NR_FR1_35MHz_45MHz_BW-Core] |
|
R4-2015703 |
CR for TS 38.104: draft CR on introduction of channel bandwidths 35MHz and 45MHz for BS TX and general part |
Huawei, HiSilicon |
R4-2015718 |
Draft CR to TS 38.104: Introduction of CBWs 35 MHz and 45 MHz |
Ericsson |
R4-2015719 |
Draft CR to TS 38.141-1: Introduction of CBWs 35 MHz and 45 MHz |
Ericsson |
R4-2015720 |
Draft CR to TS 38.141-2: Introduction of CBWs 35 MHz and 45 MHz |
Ericsson |
R4-2016114 |
Discussion on BS RF requirement for new channel bandwidth of 35MHz and 45MHz |
ZTE Corporation |
R4-2016115 |
Draft CR to TS 38.104: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016116 |
Draft CR to TS 38.141-1: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016117 |
Draft CR to TS 38.141-2: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016118 |
Draft CR to TS 37.104: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016119 |
Draft CR to 37.141: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016120 |
Draft CR to TS 37.105: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016121 |
Draft CR to 37.145-1: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016122 |
Draft CR to 37.145-2: Introduction of 35MHz and 45MHz |
ZTE Corporation |
R4-2016866 |
CR for TS 38.104: draft CR on introduction of channel bandwidths 35MHz and 45MHz for BS TX and general part |
Huawei, HiSilicon |
R4-2016867 |
Draft CR to TS 38.141-1: Introduction of CBWs 35 MHz and 45 MHz |
Ericsson |
R4-2016868 |
Draft CR to TS 38.141-2: Introduction of 35MHz and 45MHz |
ZTE Corporation |
10.22.5 |
Others [NR_FR1_35MHz_45MHz_BW-Core] |
|
R4-2014911 |
UE RF requirments tables with channel BW dependency |
Apple Inc. |
10.23 |
Band combinations for Uu and V2X con-current operation [NR_LTE_V2X_PC5_combos] |
|
R4-2016628 |
Email discussion summary for [97e][126] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
R4-2016869 |
WF on band combinations for V2X con-current operation |
CATT |
R4-2016968 |
Email discussion summary for [97e][126] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
10.23.1 |
General and Rapporteur Input (WID/TR/CR) [NR_LTE_V2X_PC5_combos-Core/Per] |
|
R4-2014421 |
Discussion on Rel-17 band combinations for Uu and V2X con-current operation |
CATT |
R4-2014425 |
Revised WID for V2X band combination |
CATT |
R4-2015561 |
TP for TR 37.875: adding some UE RF study for NR V2X band combinations |
Huawei, HiSilicon |
R4-2016870 |
TP for TR 37.875: adding some UE RF study for NR V2X band combinations |
Huawei, HiSilicon |
R4-2017829 |
TP for TR 37.875: adding some UE RF study for NR V2X band combinations |
Huawei, HiSilicon |
10.23.2 |
UE RF requirement for concurrent operation between NR Uu band and NR PC5 band [NR_LTE_V2X_PC5_combos-Core] |
|
R4-2014422 |
TP on V2X_n40A-n47A coexistence study |
CATT |
R4-2014423 |
CR for TS 38.101-1, Introduce new band combination of V2X_n39A-n47A and V2X_n40A-n47A |
CATT |
R4-2016871 |
TP on V2X_n40A-n47A coexistence study |
CATT |
R4-2016872 |
CR for TS 38.101-1, Introduce new band combination of V2X_n39A-n47A and V2X_n40A-n47A |
CATT |
10.23.3 |
UE RF requirement for concurrent operation between LTE Uu band and NR PC5 band [NR_LTE_V2X_PC5_combos-Core] |
|
R4-2014424 |
CR for TS 38.101-3, Introduce new band combination of V2X_39A-n47A, V2X_n39A-47A, V2X_40A-n47A and V2X_n40A-47A |
CATT |
R4-2016873 |
CR for TS 38.101-3, Introduce new band combination of V2X_39A-n47A, V2X_n39A-47A, V2X_40A-n47A and V2X_n40A-47A |
CATT |
10.24.1 |
UE RF (38.101-2) [NR_FR2_FWA_Bn257_Bn258-Core] |
|
R4-2014264 |
On Japan FWA EIRP requirement |
Qualcomm Incorporated |
R4-2014826 |
Proposals on FR2 FWA UE with maximum TRP of 23dBm |
MediaTek Beijing Inc. |
R4-2014832 |
Proposals on FR2 FWA UE with maximum TRP of 23dBm |
MediaTek Beijing Inc. |
R4-2015085 |
Open issues on FR2 FWA UE RF requirement |
Nokia, Nokia Shanghai Bell |
R4-2015347 |
Discussion on Rel-17 FWA |
OPPO |
R4-2015809 |
Views on RF requirement for FWA |
Sony, Ericsson |
R4-2015887 |
Views on UE RF requirements of new FWA with 23dBm maximum TRP |
Intel Corporation |
R4-2016529 |
on new FR2 FWA UE RF requirement |
Huawei, HiSilicon |
R4-2016530 |
Draft CR for FR2 FWA RF requirements |
Huawei, HiSilicon |
R4-2016629 |
Email discussion summary for [97e][127] NR_FR2_FWA_Bn257_Bn258 |
Moderator (Softbank) |
R4-2016874 |
WF on FR2 FWA RF requirements |
Softbank |
R4-2016875 |
CR for FR2 FWA RF requirements |
Huawei |
R4-2016876 |
LS for FR2 FWA power class |
RAN4 |
R4-2016969 |
Email discussion summary for [97e][127] NR_FR2_FWA_Bn257_Bn258 |
Moderator (Softbank) |
R4-2017834 |
CR for FR2 FWA RF requirements |
Huawei |
10.24.2 |
RRM Core requirements (38.133) [NR_FR2_FWA_Bn257_Bn258-Core] |
|
R4-2015480 |
DraftCR on RRM core requirements for FR2 new FWA UE in 38.133 |
Huawei, HiSilicon |
R4-2016178 |
Big CR on FR2 new FWA UE RRM requirements in 36.133 |
Ericsson |
R4-2017027 |
Email discussion summary for [97e][228] NR_FR2_FWA_Bn257_Bn258_RRM |
Moderator (Huawei) |
R4-2017261 |
DraftCR on RRM core requirements for FR2 new FWA UE in 38.133 |
Huawei, HiSilicon |
R4-2017262 |
Big CR on FR2 new FWA UE RRM requirements in TS 36.133 |
Ericsson |
R4-2017264 |
Big CR: NR FR2 new FWA UE RRM requirements (TS 38.133) |
Huawei, HiSilicon |
R4-2017298 |
Email discussion summary for [97e][228] NR_FR2_FWA_Bn257_Bn258_RRM |
Moderator (Huawei) |
10.24.3 |
RRM Perf. requirements (38.133) [NR_FR2_FWA_Bn257_Bn258-Perf] |
|
R4-2015481 |
DraftCR on RRM performance requirements for FR2 new FWA UE in 38.133 |
Huawei, HiSilicon |
R4-2017263 |
DraftCR on RRM performance requirements for FR2 new FWA UE in 38.133 |
Huawei, HiSilicon |
10.25 |
Introduction of NR band n13 [NR_n13] |
|
R4-2016630 |
Email discussion summary for [97e][128] NR_n13 |
Moderator (Huawei) |
R4-2016877 |
WF on A-MPR for NS_07 |
Apple |
R4-2016970 |
Email discussion summary for [97e][128] NR_n13 |
Moderator (Huawei) |
10.25.1 |
UE RF (38.101-1) [NR_n13-Core] |
|
R4-2014902 |
A-MPR Proposal for n13 |
Apple Inc. |
R4-2015682 |
CR to TS 38.101-1: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2016878 |
CR to TS 38.101-1: introduction of NR band n13 |
Huawei, HiSilicon |
10.25.2 |
BS RF (38.104) [NR_n13-Core] |
|
R4-2015684 |
CR to TS 38.104: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015685 |
CR to TS 38.141-1: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015686 |
CR to TS 38.141-2: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015687 |
CR to TS 36.104: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015688 |
CR to TS 36.141: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015689 |
CR to TS 37.104: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015690 |
CR to TS 37.141: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015691 |
CR to TS 37.105: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015692 |
CR to TS 37.145-1: introduction of NR band n13 |
Huawei, HiSilicon |
R4-2015693 |
CR to TS 37.145-2: introduction of NR band n13 |
Huawei, HiSilicon |
10.25.3 |
RRM (38.133) [NR_n13-Core] |
|
R4-2015683 |
CR to TS 38.133: introduction of NR band n13 |
Huawei, HiSilicon |
10.26 |
Introduction of 1880-1920MHz SUL band for NR [NR_SUL_band_1880_1920MHz] |
|
R4-2016631 |
Email discussion summary for [97e][129] NR_SUL_bands |
Moderator (CMCC) |
10.26.1 |
UE RF (38.101-1) [NR_SUL_band_1880_1920MHz-Core] |
|
R4-2014330 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.101-1 |
CMCC, Huawei, HiSilicon |
R4-2015290 |
Discussion on new SUL band n98 UE requirements |
Huawei, HiSilicon |
10.26.2 |
BS RF (38.104) [NR_SUL_band_1880_1920MHz -Core] |
|
R4-2014331 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.104 |
CMCC, Huawei, HiSilicon |
R4-2014332 |
Introduction of 1880-1920MHz SUL band into Rel-16 TS 36.104 |
CMCC, Huawei, HiSilicon |
R4-2014333 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 36.141 |
CMCC, Huawei, HiSilicon |
R4-2014334 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.104 |
CMCC, Huawei, HiSilicon |
R4-2014335 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.105 |
CMCC, Huawei, HiSilicon |
R4-2014336 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.141 |
CMCC, Huawei, HiSilicon |
R4-2014337 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.145-1 |
CMCC, Huawei, HiSilicon |
R4-2014338 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 37.145-2 |
CMCC, Huawei, HiSilicon |
R4-2014339 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.141-1 |
CMCC, Huawei, HiSilicon |
R4-2014340 |
Introduction of 1880-1920MHz SUL band into Rel-17 TS 38.141-2 |
CMCC, Huawei, HiSilicon |
R4-2015291 |
Discussion on new SUL band n98 BS requirements |
Huawei, HiSilicon |
10.27.1 |
UE RF (38.101-1) [NR_SUL_band_2300_2400MHz -Core] |
|
R4-2014341 |
introduction of 2300-2400MHz SUL band into Rel-17 TS 38.101-1 |
CMCC, Huawei, HiSilicon |
R4-2015288 |
Discussion on new SUL band n97 UE requirements |
Huawei, HiSilicon |
10.27.2 |
BS RF (38.104) [NR_SUL_band_2300_2400MHz -Core] |
|
R4-2014342 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.104 |
CMCC, Huawei, HiSilicon |
R4-2014343 |
Introduction of 2300-2400MHz SUL band into Rel-16 TS 36.104 |
CMCC, Huawei, HiSilicon |
R4-2014344 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 36.141 |
CMCC, Huawei, HiSilicon |
R4-2014345 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.104 |
CMCC, Huawei, HiSilicon |
R4-2014346 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.105 |
CMCC, Huawei, HiSilicon |
R4-2014347 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.141 |
CMCC, Huawei, HiSilicon |
R4-2014348 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.145-1 |
CMCC, Huawei, HiSilicon |
R4-2014349 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 37.145-2 |
CMCC, Huawei, HiSilicon |
R4-2014350 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.141-1 |
CMCC, Huawei, HiSilicon |
R4-2014351 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.141-2 |
CMCCCMCC, Huawei, HiSilicon |
R4-2014355 |
Introduction of 2300-2400MHz SUL band into Rel-17 TS 38.141-2 |
CMCC, Huawei, HiSilicon |
R4-2015289 |
Discussion on new SUL band n97 BS requirements |
Huawei, HiSilicon |
10.28 |
Introduction of NR 47 GHz band [NR_47GHz_Band] |
|
R4-2016461 |
Revised WID: introduction of NR 47 GHz band |
T-Mobile USA, Dish Network |
R4-2016632 |
Email discussion summary for [97e][130] NR_47GHz_Band |
Moderator (Nokia) |
R4-2016879 |
WF on UE RF requirement of n262 |
Qualcomm, Nokia, Sony |
R4-2016880 |
WF on multi-band relaxation of n262 |
Apple |
R4-2016881 |
WF on BS MU/TT for n262 |
Nokia |
R4-2016971 |
Email discussion summary for [97e][130] NR_47GHz_Band |
Moderator (Nokia) |
10.28.1 |
UE RF (38.101-2) [NR_47GHz_Band -Core] |
|
R4-2014263 |
Discussion on PC3 EIRP and EIS in n262 |
Qualcomm Incorporated |
R4-2015084 |
UE RF requirements for NR band n262 |
Nokia, Nokia Shanghai Bell |
R4-2015855 |
Link budget for PC3 for n262 |
Sony, Ericsson |
R4-2015888 |
PC3 minimum peak EIRP and EIS requirements for band n262 |
Intel Corporation |
R4-2015894 |
Link budget for PC3 for n262 |
Sony, Ericsson |
R4-2015896 |
Link budget for PC3 for n262 |
Sony, Ericsson |
R4-2016229 |
EIRP and EIS evaluation for band n262 |
vivo |
R4-2016296 |
Peak EIRP and Peak EIS for band n262 |
Apple Inc. |
10.28.2 |
BS RF (38.104) [NR_47GHz_Band -Core] |
|
R4-2015903 |
Draft CR to TS 38.104 |
Ericsson |
R4-2015904 |
BS RF requirements and system parameters - TP to TR 38.847 |
Ericsson |
R4-2016155 |
47GHz band TT for NR BS RF requirement |
Keysight Technologies UK Ltd |
R4-2016191 |
TP to TR 38.847: BS RF requirements |
Nokia, Nokia Shanghai Bell |
R4-2016882 |
Draft CR to TS 38.104 |
Ericsson, Nokia, Nokia Shanghai Bell |
R4-2016883 |
BS RF requirements and system parameters - TP to TR 38.847 |
Ericsson |
R4-2016884 |
TP to TR 38.847: BS RF requirements |
Nokia, Nokia Shanghai Bell |
10.28.3 |
RRM (38.133) [NR_47GHz_Band -Core] |
|
R4-2016179 |
Analysis of RRM requirements for 47 GHz band |
Ericsson |
10.28.4 |
Others [NR_47GHz_Band -Core/Perf] |
|
R4-2015083 |
TP to TR 38.847 on regulatory background and system parameters |
Nokia, Nokia Shanghai Bell |
R4-2015902 |
TR 38.847 Introduction of NR Band 262 (47Ghz band) |
Ericsson |
R4-2016096 |
Simulation results on UE demodulation performance impact by the introduction of NR 47GHz band |
Ericsson |
R4-2016097 |
On demodulation requirements for the new 47GHz band |
Ericsson |
10.29 |
Introduction of NR band n24 [NR_band_n24] |
|
R4-2016633 |
Email discussion summary for [97e][131] NR_LTE_band_n24 |
Moderator (Ligado Networks) |
R4-2016896 |
WF on work items LTE_B24_mod and NR_band_n24 |
Ligado Networks |
R4-2016897 |
WF on work item NR_SUL_UL_n24) |
Ligado Networks |
R4-2016972 |
Email discussion summary for [97e][131] NR_LTE_band_n24 |
Moderator (Ligado Networks) |
10.29.1 |
UE RF (38.101-1) [NR_band_n24-Core] |
|
R4-2014466 |
n24 emission requirements and A-MPR assumptions |
Ligado Networks |
R4-2014495 |
Band 24 and n24 A-MPR |
Skyworks Solutions Inc. |
10.29.2 |
BS RF (38.104) [NR_band_n24-Core] |
|
R4-2016192 |
Draft CR to 36.104: Introduction of n24 requirements |
Nokia, Nokia Shanghai Bell |
R4-2016193 |
Draft CR to 36.141: Introduction of n24 requirements |
Nokia, Nokia Shanghai Bell |
R4-2016194 |
Draft CR to 37.104: Introduction of n24 requirements |
Nokia, Nokia Shanghai Bell |
R4-2016195 |
Draft CR to 37.141: Introduction of n24 requirements |
Nokia, Nokia Shanghai Bell |
R4-2016196 |
Draft CR to 38.104: Introduction of n24 |
Nokia, Nokia Shanghai Bell |
R4-2016895 |
Draft CR to 38.104: Introduction of n24 |
Nokia, Nokia Shanghai Bell |
10.29.4 |
Others [NR_band_n24-Core/Perf] |
|
R4-2014176 |
Draft CR for 37.105 Introduction of NR band n24 |
Ligado Networks |
R4-2014177 |
Draft CR for 37.145-1 Introduction of NR band n24 |
Ligado Networks |
R4-2014178 |
Draft CR for 37.145-2 Introduction of NR band n24 |
Ligado Networks |
R4-2014179 |
Draft CR for 38.141-1 Introduction of NR band n24 |
Ligado Networks |
R4-2014180 |
Draft CR for 38.141-2 Introduction of NR band n24 |
Ligado Networks |
R4-2016892 |
Draft CR for 37.145-1 Introduction of NR band n24 |
Ligado Networks |
R4-2016893 |
Draft CR for 38.141-1 Introduction of NR band n24 |
Ligado Networks |
R4-2016894 |
Draft CR for 38.141-2 Introduction of NR band n24 |
Ligado Networks |
10.30 |
Introduction of 1.6 GHz NR SUL band with same uplink frequency range of Band 24 [NR_SUL_UL_n24] |
|
R4-2015356 |
Discussion on the new SUL band for 1.6GHz |
Huawei,HiSilicon |
10.30.1 |
UE RF (38.101-1) [NR_SUL_UL_n24-Core] |
|
R4-2014468 |
A-MPR and Emission Requirements for new SUL Band related to the UL of n24 |
Ligado Networks |
R4-2015357 |
draftCR to 38101-1 on introducing new SUL band n99 |
Huawei,HiSilicon |
10.30.2 |
BS RF (38.104) [NR_SUL_UL_n24-Core] |
|
R4-2014202 |
Draft CR for TS 38.104 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2015358 |
draftCR to 38104 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015359 |
draftCR to 36104 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015360 |
draftCR to 38141-1 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015361 |
draftCR to 38141-2 on introducing new SUL band n96 |
Huawei,HiSilicon |
R4-2015362 |
draftCR to 36141 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015363 |
draftCR to 37104 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015364 |
draftCR to 37141 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015365 |
draftCR to 37105 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015366 |
draftCR to 37145-1 on introducing new SUL band n99 |
Huawei,HiSilicon |
R4-2015367 |
draftCR to 37145-2 on introducing new SUL band n99 |
Huawei,HiSilicon |
10.30.4 |
Others [NR_SUL_UL_n24-Core/Perf] |
|
R4-2014203 |
Draft CR for TS 36.104 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014204 |
Draft CR for TS 36.141 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014205 |
Draft CR for TS 37.104 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014206 |
Draft CR for TS 37.105 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014207 |
Draft CR for TS 37.141 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014208 |
Draft CR for TS 37.145-1 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014209 |
Draft CR for TS 37.145-2 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014210 |
Draft CR for TS 38.141-1 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2014211 |
Draft CR for TS 38.141-2 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2016898 |
Draft CR for TS 37.105 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2016899 |
Draft CR for TS 37.141 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
R4-2016900 |
Draft CR for TS 37.145-1 Introduction of SUL for UL of NR band n24 |
Ligado Networks |
11.1 |
Study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz [FS_6425_10500MHz _NR] |
|
R4-2015675 |
TR 38.921 V 0.2.0 |
Huawei, HiSilicon |
R4-2015681 |
Draft reply LS on Parameters of terrestrial component of IMT for sharing and compatibility studies in preparation for WRC-23 (6.425 to 10.5 GHz) |
Huawei, HiSilicon |
R4-2016132 |
Maintenance TP to TR38.921 |
ZTE Corporation |
R4-2016634 |
Email discussion summary for [97e][132] FS_6425_10500MHz _NR |
Moderator (Ericsson) |
R4-2016903 |
Maintenance TP to TR38.921 |
ZTE Corporation |
R4-2016904 |
WF on Coexistence Simulations results for 6.425-7.125 GHz and 10.0-10.5 GHz |
Huawei, HiSilicon, CATT, Nokia, Ericsson, ZTE |
R4-2016905 |
WF on BS and UE parameters for 6.425-7.125 and 10.0-10.5 GHz |
Nokia, CATT, Ericsson, ZTE, Huawei, Qualcomm |
R4-2016973 |
Email discussion summary for [97e][132] FS_6425_10500MHz _NR |
Moderator (Ericsson) |
11.1.1 |
UE parameters |
|
R4-2014456 |
UE parameters for the frequency range 6.425-7.125GHz, 7.025-7.125GHz and 10.0-10.5GHz |
CATT |
R4-2014473 |
Proposals of UE Parameters for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2015676 |
TP on UE IMT technology related parameters |
Huawei, HiSilicon |
R4-2015900 |
SI on IMT parameters - Remaining UE parameters |
Ericsson |
11.1.2 |
BS parameters |
|
R4-2014457 |
BS parameters for the frequency range 6.425-7.125GHz, 7.025-7.125GHz and 10.0-10.5GHz |
CATT |
R4-2014474 |
Proposals of BS Parameters for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2014738 |
Discussion on remaining issues for 6425-7125 BS parameter |
CMCC |
R4-2014749 |
Discussion on remaining issues for 6425-7125 BS parameter |
CMCC |
R4-2015677 |
TP on BS remaining parameters |
Huawei, HiSilicon |
R4-2015899 |
SI on IMT parameters - Remaining BS parameters |
Ericsson |
R4-2016133 |
TP to TR38.921 : BS spurious emission |
ZTE Corporation |
R4-2016369 |
LS to ECC SE21 on Spurious emission limits for AAS BS in 6.425 - 7.125 GHz and 10-10.5 GHz |
RAN4 |
R4-2016906 |
TP to TR38.921 : BS spurious emission |
ZTE Corporation |
11.1.3.1 |
Simulation assumptions |
|
R4-2014475 |
TP to TR 38.921: Clarification of system level simulation assumptions for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell, ZTE |
R4-2015901 |
SI on IMT parameters - Simulation assumptions |
Ericsson |
R4-2016901 |
TP to TR 38.921: Clarification of system level simulation assumptions for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell, ZTE |
11.1.3.2 |
Downlink |
|
R4-2014458 |
Simulation results for 6425-7125MHz and 10-10.5GHz-downlink |
CATT |
R4-2014476 |
Downlink Coexistence Simulation Results for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2015678 |
Simulation results on DL co-existence for 6.425-7.125GHz, 10.0-10.5 GHz |
Huawei, HiSilicon |
R4-2015897 |
SI on IMT parameters - DL simulations results |
Ericsson |
R4-2016134 |
DL simulation results for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
R4-2016236 |
Downlink co-existence simulation results for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Qualcomm Incorporated |
R4-2016777 |
Simulation results for 6425-7125MHz and 10-10.5GHz-downlink |
CATT |
11.1.3.3 |
Uplink |
|
R4-2014459 |
Simulation results for 6425-7125MHz and 10-10.5GHz-uplink |
CATT |
R4-2014477 |
Uplink Coexistence Simulation Results for Frequency Ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell |
R4-2015679 |
Simulation results on UL co-existence for 6.425-7.125GHz, 10.0-10.5 GHz |
Huawei, HiSilicon |
R4-2015898 |
SI on IMT parameters - UL simulations results |
Ericsson |
R4-2016135 |
UL simulation results for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
R4-2016136 |
TP to TR38.921: uplink ACIR model |
ZTE Corporation |
R4-2016237 |
Uplink co-existence simulation results for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Qualcomm Incorporated |
R4-2016601 |
Uplink co-existence simulation results for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Qualcomm Incorporated |
R4-2016778 |
Simulation results for 6425-7125MHz and 10-10.5GHz-uplink |
CATT |
R4-2017817 |
TP to TR38.921: uplink ACIR model |
ZTE Corporation |
11.1.4 |
Antenna characteristics |
|
R4-2014478 |
TP to TR 38.921: Clarification of BS array antenna element peak gain for study on IMT parameters for frequency ranges 6.425-7.125GHz and 10.0-10.5GHz |
Nokia, Nokia Shanghai Bell, ZTE |
R4-2014979 |
TP to TR 38.921: Correction to antenna parameter table in clause 3 and sub-clause 8.1 |
Ericsson |
R4-2016902 |
TP to TR 38.921: Correction to antenna parameter table in clause 3 and sub-clause 8.1 |
Ericsson |
11.1.5 |
Relevant information for the sharing and compatibility studies |
|
R4-2014978 |
On AAS base station array antenna model and spatial selectivity |
Ericsson |
R4-2015680 |
TP on spatial emission and interference mitigation |
Huawei, HiSilicon |
R4-2016907 |
TP on spatial emission and interference mitigation |
Huawei, HiSilicon |
12.1.1 |
General [NR_MIMO_OTA] |
|
R4-2015311 |
Framework on NR MIMO OTA requirements development |
CAICT,vivo |
R4-2016216 |
TS 38.151 v0.1.0 NR MIMO OTA requirements |
vivo |
R4-2016217 |
LS on FR1 MIMO OTA |
vivo, CAICT |
R4-2016218 |
TP to TS 38.151 v0.0.1 on general part |
vivo, CAICT |
R4-2016588 |
Discussion on MIMO OTA framework |
Huawei, HiSilicon |
R4-2017428 |
Email discussion summary for [97e][330] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2017583 |
LS on FR1 MIMO OTA |
RAN4 |
R4-2017585 |
WF on NR MIMO OTA |
vivo, CAICT |
R4-2017629 |
Email discussion summary for [97e][330] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2017632 |
WF on FR2 MIMO OTA simulation assumption |
Huawei |
12.1.2 |
Performance Requirements [NR_MIMO_OTA-Core] |
|
R4-2014829 |
Proposal of FR2 MIMO OTA simulation approach workplan |
MediaTek Beijing Inc. |
12.1.2.1 |
Performance Requirements for FR1 [NR_MIMO_OTA-Core] |
|
R4-2016209 |
On FR1 4x4 vs. 2x2 channel models |
Keysight Technologies UK Ltd |
R4-2016220 |
Channel model simulation for FR1 performance requirement |
vivo |
12.1.2.2 |
Performance Requirements for FR2 [NR_MIMO_OTA-Core] |
|
R4-2015352 |
Analysis on the impact of number of test points |
OPPO |
R4-2016208 |
On FR2 MIMO OTA channel model down selection |
Keysight Technologies UK Ltd |
R4-2016219 |
Discussions on FR2 MIMO OTA requirements |
vivo, CAICT |
R4-2016235 |
Views on for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2016539 |
Simulation assumptions for NR FR2 MIMO OTA |
Huawei, HiSilicon |
12.1.3 |
Testing methodologies [NR_MIMO_OTA-Core] |
|
R4-2014688 |
Effect of White Box Approach on Simple-Sectored Multi-Probe Anechoic Chamber Design |
BUPT |
R4-2014710 |
Effect of White Box Approach on Simple-Sectored Multi-Probe Anechoic Chamber Design |
BUPT |
R4-2015368 |
Discussion on MIMO OTA test methodologies |
Huawei,HiSilicon |
12.1.3.1 |
Testing parameters for Performance [NR_MIMO_OTA-Core] |
|
R4-2014723 |
Discussion on FR1 and FR2 MIMO OTA |
Samsung |
R4-2016222 |
TP to TS 38.151 v0.0.1 on FR1 test system for requirements |
vivo, CAICT |
R4-2016589 |
Discussion on MIMO OTA open issues |
Huawei, HiSilicon |
12.1.3.2 |
Optimization of test methodologies [NR_MIMO_OTA-Core] |
|
R4-2015258 |
on UE orientation clarification |
Xiaomi |
R4-2015353 |
The rules for 3D-MPAC system implementation |
OPPO |
R4-2016210 |
On Probe Configurations and Channel model vs. OTA test system coordinate systems for FR2 MIMO OTA |
Keysight Technologies UK Ltd |
12.1.3.3 |
Channel model validation [NR_MIMO_OTA-Core] |
|
R4-2014536 |
Channel Model Assumptions |
Spirent Communications |
R4-2016221 |
TP to TS 38.151 v0.0.1 on FR1 Channel model and RMC |
vivo, CAICT, Spirent |
R4-2016561 |
FR1 MIMO OTA channel model validation results |
CAICT,Keysight,vivo |
R4-2017584 |
TP to TS 38.151 v0.0.1 on FR1 Channel model and RMC |
vivo, CAICT, Spirent |
12.2.1 |
General and work plan [NR_RF_FR1_enh -Core] |
|
R4-2016540 |
work plan for Rel-17 FR1 UE RF enhancement |
Huawei, HiSilicon |
R4-2016635 |
Email discussion summary for [97e][133] NR_RF_FR1_enh_Part_1 |
Moderator (Huawei) |
R4-2016908 |
work plan for Rel-17 FR1 UE RF enhancement |
Huawei, HiSilicon |
R4-2016910 |
WF on MPR simulation assumption for PC2 intra-band contiguous UL CA |
Skyworks |
R4-2016911 |
WF on RF requirements for PC2 intra-band contiguous UL CA |
Huawei |
R4-2016912 |
WF on 4Rx requirement for CA_n77(3A) and CA_77(4A) |
Softbank |
R4-2016974 |
Email discussion summary for [97e][133] NR_RF_FR1_enh_Part_1 |
Moderator (Huawei) |
R4-2017827 |
WF on RF requirements for PC2 intra-band contiguous UL CA |
Huawei |
R4-2017842 |
Email discussion summary for [97e][133] NR_RF_FR1_enh_Part_1 |
Moderator (Huawei) |
12.2.2.1 |
UL MIMO configuration for SUL band configurations [NR_RF_FR1_enh -Core] |
|
R4-2014735 |
Draft CR: Introduce NR SUL bands n80 to UL-MIMO configuration |
CMCC |
R4-2014736 |
LS on removing restriction on configuring UL MIMO for SUL band |
CMCC |
R4-2015181 |
Considerations on enabling UL-MIMO support for SUL |
ZTE Wistron Telecom AB |
R4-2015284 |
Removing restrictions on SUL UL-MIMO in Rel-17 |
Huawei, HiSilicon |
R4-2016909 |
LS on removing restriction on configuring UL MIMO for SUL band |
RAN4 |
12.2.2.2 |
2Tx switching between carrier 1 and carrier 2 [NR_RF_FR1_enh -Core] |
|
R4-2014465 |
Discussion on 2Tx switching between carrier 1 and carrier 2 |
CATT |
R4-2014717 |
Discussion on 2Tx-2tx switching comapred to the 1Tx-2Tx case |
Qualcomm Incorporated |
R4-2014739 |
UL Tx switching related RF requirements for R17 new scenarios |
CMCC |
R4-2015182 |
Initial considerations on 2Tx switching between 2 carriers |
ZTE Wistron Telecom AB |
R4-2015197 |
Discussion on 2Tx switching between carrier 1 and carrier 2 |
China Telecom |
R4-2015262 |
consideration on UL Tx switching enhancement in Rel 17 |
Xiaomi |
R4-2015283 |
Discussion on the introduction of 2Tx - 2Tx UE uplink switch |
Huawei, HiSilicon |
R4-2015325 |
Enhancment of Tx Switching in R17 |
vivo |
R4-2015355 |
Discussion on Rel-17 FR1 Tx switching |
OPPO |
R4-2016636 |
Email discussion summary for [97e][134] NR_RF_FR1_enh_Part_2 |
Moderator (China Telecom) |
R4-2016914 |
WF on RF requirements for Rel-17 Tx switching enhancement |
China Telecom |
R4-2016975 |
Email discussion summary for [97e][134] NR_RF_FR1_enh_Part_2 |
Moderator (China Telecom) |
R4-2017815 |
WF on RF requirements for Rel-17 Tx switching enhancement |
China Telecom |
12.2.2.3 |
Tx switching between 1 carrier on band A and 2 contiguous aggregated carriers on band B [NR_RF_FR1_enh -Core] |
|
R4-2015198 |
Discussion on Tx switching between 1 carrier on band A and 2 contiguous aggregated carriers on band B |
China Telecom |
12.2.2.4 |
HPUE for TDD intra-band contiguous UL CA [NR_RF_FR1_enh -Core] |
|
R4-2014175 |
HPUE TDD+TDD considerations |
Qualcomm Incorporated |
R4-2014392 |
Discussion on SAR solutions of TDD intra-band contiguous UL CA HPUE |
CATT |
R4-2014508 |
PC2 UL CA Class B/C UE Architecture and MPR/A-MPR evaluation |
Skyworks Solutions Inc., Apple Inc. |
R4-2015038 |
Discussion on PC2 intra-band contiguous NR CA |
ZTE Corporation |
R4-2015261 |
Discussion on HP UE for TDD intra-band contiguous UL CA |
Xiaomi |
R4-2015326 |
Discussion on HPUE for TDD intra-band contiguous UL CA |
vivo |
R4-2015354 |
Discussion on Rel-17 FR1 intra-band contiguous HPUE |
OPPO |
R4-2016537 |
on intra-band CA HPUE RF architecture |
Huawei, HiSilicon |
12.3.1 |
General and work plan [NR_RF_FR2_req_enh2-Core] |
|
R4-2014513 |
TR skeleton for Rel-17 FR2 UE RF WI |
Nokia, Nokia Shanghai Bell |
R4-2014514 |
Work plan for New WID on NR RF Enhancements for FR2 |
Nokia, Nokia Shanghai Bell |
R4-2016637 |
Email discussion summary for [97e][135] NR_RF_FR2_req_enh2_Part_1 |
Moderator (Nokia) |
R4-2016915 |
WF on Applicability of CBM/IBM for different CA |
Samsung |
R4-2016916 |
WF on UE requirements for CA configurations CA_n258A-n260A and CA_n257A-n259A based on IBM |
Intel |
R4-2016917 |
WF on UE requirements for CA configurations within the same frequency group based on CBM |
Nokia |
R4-2016976 |
Email discussion summary for [97e][135] NR_RF_FR2_req_enh2_Part_1 |
Moderator (Nokia) |
12.3.2 |
RF core requirements [NR_RF_FR2_req_enh2-Core] |
|
R4-2014724 |
Discussion on Rel-17 FR2 inter-band CA |
Samsung |
12.3.2.1 |
Inter-band DL CA enhancements [NR_RF_FR2_req_enh2-Core] |
|
R4-2014912 |
More on FR2 Inter-band DL CA |
Apple Inc. |
R4-2015327 |
Discussion on FR2 inter-band DL CA enhancements |
vivo |
12.3.2.1.1 |
Applicability of CBM/IBM for different CA configurations [NR_RF_FR2_req_enh2-Core] |
|
R4-2014293 |
Inter-band DL CA CBM band pairs for FR2 Rel-17 |
Qualcomm Incorporated |
R4-2014515 |
FR2 interband CA CBM vs IBM |
Nokia, Nokia Shanghai Bell |
R4-2014586 |
CBM IBM Applicability for Inter-Band DL CA |
Intel Corporation |
R4-2015348 |
Discussion on Rel-17 FR2 inter-band DL CA |
OPPO |
R4-2016344 |
Views on applicability of CBM/IBM for different CA configurations |
Ericsson, Sony |
R4-2016523 |
On Rel-17 inter band DL CA_FR2 |
Huawei, HiSilicon |
12.3.2.1.2 |
Feasibility study for CA configurations within same frequency group based on IBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2014233 |
On the feasibility of IBM for FR2 inter-band CA within the same frequency group |
Apple |
R4-2014587 |
On IBM feasibility for CA configurations within same frequency group |
Intel Corporation |
R4-2015873 |
Views on Feasibility for CA configurations within same frequency group based on IBM |
Sony, Ericsson |
R4-2016638 |
Email discussion summary for [97e][136] NR_RF_FR2_req_enh2_Part_2 |
Moderator (Qualcomm) |
R4-2016918 |
WF on inter-band CA and UE BM type |
Qualcomm |
R4-2016977 |
Email discussion summary for [97e][136] NR_RF_FR2_req_enh2_Part_2 |
Moderator (Qualcomm) |
R4-2017813 |
WF on inter-band CA and UE BM type |
Qualcomm |
12.3.2.1.3 |
Feasibility study for CA configurations between different frequency groups based on CBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2014232 |
On the feasibility of CBM for FR2 inter-band CA cross different frequency groups |
Apple |
R4-2015874 |
Views on Feasibility for CA configurations between different frequency groups based on CBM |
Sony, Ericsson |
12.3.2.1.4 |
UE requirements for CA configurations CA_n258A-n260A and CA_n257A-n259A based on IBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2014589 |
UE requirements for CA_258A-n260A and CA_257A-n259A based on IBM |
Intel Corporation |
R4-2014966 |
DL Inter-band CA_n257-n259 |
NTT DOCOMO INC. |
R4-2015875 |
Views on Rel-17 inter-band DL CA in FR2 |
Sony, Ericsson |
12.3.2.1.5 |
UE requirements for CA configurations within the same frequency group based on CBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2014588 |
UE requirements for CA configurations within the same frequency group based on CBM |
Intel Corporation |
12.3.2.2 |
Inter-band UL CA [NR_RF_FR2_req_enh2-Core] |
|
R4-2014913 |
Views on FR2 Inter-band UL CA |
Apple Inc. |
R4-2015328 |
Discussion on FR2 inter-band UL CA |
vivo |
12.3.2.2.2 |
Feasibility study for CA configurations between different frequency groups based on CBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2014715 |
Inter-band UL CA for FR2 |
Qualcomm Incorporated |
12.3.2.2.3 |
UE requirements for CA configuration CA_n257A-n259A based on IBM [NR_RF_FR2_req_enh2-Core] |
|
R4-2016086 |
UL inter-band CA for different band group based on IBE |
NTT DOCOMO INC. |
12.3.2.3 |
UL gaps for self-calibration and monitoring [NR_RF_FR2_req_enh2-Core] |
|
R4-2014218 |
Discusison on UL gaps for self-calibration/monitoring |
Apple |
R4-2014393 |
Discussion on UL gaps for self-calibration and monitoring |
CATT |
R4-2014516 |
FR2 gaps |
Nokia, Nokia Shanghai Bell |
R4-2014590 |
On performance improvements from self-calibration in UL gaps |
Intel Corporation |
R4-2014716 |
UE calibration gap motivation and view to the requirements |
Qualcomm Incorporated |
R4-2014963 |
Discussion on UL gap for self-calibration and monitoring |
vivo |
R4-2015349 |
Discussion on Rel-17 FR2 calibration gap |
OPPO |
R4-2016061 |
Analysis on power calibration gaps |
Ericsson, Sony |
R4-2016536 |
on gaps for self-calibration and monitoring |
Huawei, HiSilicon |
R4-2016560 |
Further discusison on UL gaps for self-calibration and monitoring |
Apple |
R4-2016639 |
Email discussion summary for [97e][137] NR_RF_FR2_req_enh2_Part_3 |
Moderator (Apple) |
R4-2016919 |
WF on UL gap in FR2 |
Apple |
R4-2016978 |
Email discussion summary for [97e][137] NR_RF_FR2_req_enh2_Part_3 |
Moderator (Apple) |
12.4 |
NR RRM further enhancement [NR_RRM_enh2-Core] |
|
R4-2017028 |
Email discussion summary for [97e][229] NR_RRM_enh2 |
Moderator (Apple) |
R4-2017299 |
Email discussion summary for [97e][229] NR_RRM_enh2 |
Moderator (Apple) |
12.4.1 |
Work plan [NR_RRM_enh2-Core] |
|
R4-2014286 |
Work plan for R17 FeRRM |
Apple |
R4-2015310 |
Views on PUCCH SCell Activation/Deactivation delay requirements |
NTT DOCOMO, INC. |
R4-2017265 |
Work plan for R17 FeRRM |
Apple |
12.5 |
NR measurement gap enhancements [NR_MG_enh-Core] |
|
R4-2017029 |
Email discussion summary for [97e][230] NR_MG_enh |
Moderator (MediaTek) |
R4-2017300 |
Email discussion summary for [97e][230] NR_MG_enh |
Moderator (MediaTek) |
12.5.1 |
Work plan [NR_MG_enh-Core] |
|
R4-2014224 |
Work plan for measurement gap enhancement |
Apple |
R4-2014628 |
Work plan of R17 NR and MR-DC measurement gap enhancements WI |
MediaTek inc., Intel Corporation |
R4-2017266 |
Work plan of R17 NR and MR-DC measurement gap enhancements WI |
MediaTek inc., Intel Corporation |
12.6 |
Enhancement for NR high speed train scenario in FR1 [NR_HST_FR1_enh-Core] |
|
R4-2017030 |
Email discussion summary for [97e][231] NR_HST_FR1_enh |
Moderator (CMCC) |
R4-2017301 |
Email discussion summary for [97e][231] NR_HST_FR1_enh |
Moderator (CMCC) |
12.6.1 |
Work plan [NR_HST_FR1_enh-Core] |
|
R4-2014225 |
Work plan for NR high speed train scenario in FR1 |
Apple |
R4-2014705 |
Work plan for enhancement for NR high speed train scenario in FR1 |
CMCC |
R4-2017267 |
Work plan for enhancement for NR high speed train scenario in FR1 |
CMCC |
12.7 |
NR support for high speed train scenario in FR2 [NR_HST_FR2_enh] |
|
R4-2016640 |
Email discussion summary for [97e][138] NR_HST_FR2_enh |
Moderator (Samsung) |
R4-2016921 |
WF on NR support for HST in FR2 |
Samsung |
R4-2016979 |
Email discussion summary for [97e][138] NR_HST_FR2_enh |
Moderator (Samsung) |
R4-2017828 |
WF on NR support for HST in FR2 |
Samsung |
12.7.1 |
General and work plan [NR_HST_FR2_enh-Core] |
|
R4-2014846 |
Work plan for NR support for high speed train scenario in FR2 |
Samsung, Nokia, Nokia Shanghai Bell |
R4-2015859 |
General considerations for FR2 HST |
Ericsson |
R4-2015880 |
TR skeleton for NR support for high speed train scenario in FR2 |
Nokia, Nokia Shanghai Bell |
R4-2016920 |
Work plan for NR support for high speed train scenario in FR2 |
Samsung, Nokia, Nokia Shanghai Bell |
R4-2016922 |
TR skeleton for NR support for high speed train scenario in FR2 |
Nokia, Nokia Shanghai Bell |
R4-2017838 |
TR skeleton for NR support for high speed train scenario in FR2 |
Nokia, Nokia Shanghai Bell, Samsung |
12.7.2 |
High speed train deployment scenario in FR2 [NR_HST_FR2_enh-Core] |
|
R4-2014564 |
Views on high speed train deployments scenarios in FR2 |
Intel Corporation |
R4-2014632 |
FR2 HST analysis framework |
Qualcomm, Inc. |
R4-2014834 |
Discussion on scenarios for FR2 high speed train |
Verizon, Samsung |
R4-2014847 |
Discussion on high speed train deployment scenario in FR2 |
Samsung |
R4-2015614 |
Discussion on high speed train deployment scenario in FR2 |
Huawei, HiSilicon |
R4-2015860 |
Deployment scenarios for FR2 HST |
Ericsson |
R4-2016387 |
On the high-speed train deployment scenario in FR2 |
Nokia, Nokia Shanghai Bell |
12.7.3 |
UE RF core requirements [NR_HST_FR2_enh-Core] |
|
R4-2014848 |
Discussion on UE RF requirement for FR2 HST |
Samsung |
R4-2015087 |
Power Class 4 for HST |
Nokia, Nokia Shanghai Bell |
R4-2016058 |
On UE Core requirements for FR2 HST |
Ericsson |
R4-2016538 |
on RF requirement for NR FR2 HST |
Huawei, HiSilicon |
12.8.1 |
General and work plan [NR_NTN_solutions] |
|
R4-2014066 |
On the status of NTN in 3GPP |
Fraunhofer HHI, Fraunhofer IIS |
R4-2014381 |
NR_NTN_solutions work plan |
THALES |
R4-2014785 |
Views on NTN bands and coexistence study |
Samsung |
R4-2014880 |
Discussion on the applicability of DFT-S-OFDM for NTN |
CAICT |
R4-2015905 |
Specification structure for NTN nodes |
Ericsson |
R4-2017410 |
Email discussion summary for [97e][312] NTN_Solutions |
Moderator (THALES) |
R4-2017600 |
WF on NTN solutions |
THALES |
R4-2017630 |
Email discussion summary for [97e][312] NTN_Solutions |
Moderator (THALES) |
R4-2017661 |
NR_NTN_solutions work plan |
THALES |
12.8.2 |
Use cases, deployment scenarios, and regulatory information [NR_NTN_solutions-Core] |
|
R4-2014467 |
Possible FR2 exemplary band for NR based satellite networks |
HUGHES Network Systems Ltd, Thales |
R4-2015252 |
NTN - On use cases and deployment scenarios |
Nokia, Nokia Shanghai Bell |
R4-2015263 |
Initial discussion for NR to support non-terrestrial networks |
Xiaomi |
R4-2015547 |
General discussion about NTN topic |
Huawei, HiSilicon |
R4-2015906 |
NTN Scenarios and Regulatory overview |
Ericsson |
R4-2015913 |
NTN use case scenarios and architectures |
THALES |
R4-2015915 |
Possible FR1 exemplary band for NR satellite networks |
THALES |
12.8.3 |
Coexistence aspects [NR_NTN_solutions -Core] |
|
R4-2015945 |
NTN Proposed RF Core Requirements |
THALES |
12.8.3.1 |
Simulation assumptions [NR_NTN_solutions -Core] |
|
R4-2015548 |
General discussion on NTN simulation assumptions |
Huawei, HiSilicon |
R4-2015907 |
NTN Simulations discussion |
Ericsson |
R4-2016112 |
Discussion on simulation assumptions for NTN coexistence study |
ZTE Corporation |
12.8.3.3 |
BS requirements aspects [NR_NTN_solutions -Core] |
|
R4-2015908 |
NTN coexistence - BS requirements aspects |
Ericsson |
12.8.4 |
RRM requirements [NR_NTN_solutions-Core] |
|
R4-2014658 |
Initial discussion on RRM impact for NR NTN system |
Xiaomi |
R4-2014875 |
Discussion on RRM requirements in NTN |
MediaTek inc. |
R4-2014928 |
Satellite Position Accuracy |
Eutelsat S.A. |
R4-2015730 |
Initial discussion on NTN RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2015946 |
NTN RRM and Demodulation KPIs |
THALES |
R4-2016037 |
NTN impact on RRM |
Ericsson |
R4-2017031 |
Email discussion summary for [97e][232] NR_NTN_solutions_RRM |
Moderator (THALES) |
R4-2017268 |
WF on NR NTN RRM requirements |
THALES |
R4-2017302 |
Email discussion summary for [97e][232] NR_NTN_solutions_RRM |
Moderator (THALES) |
R4-2017350 |
WF on NR NTN RRM requirements |
THALES |
12.9 |
UE Power Saving Enhancements [NR_UE_pow_sav_enh] |
|
R4-2017032 |
Email discussion summary for [97e][233] NR_UE_pow_sav_enh_RRM |
Moderator (MediaTek) |
R4-2017303 |
Email discussion summary for [97e][233] NR_UE_pow_sav_enh_RRM |
Moderator (MediaTek) |
12.9.1 |
General and work plan [NR_UE_pow_sav_enh] |
|
R4-2014366 |
Work plan of Rel-17 Power Saving Enhancements |
MediaTek inc. |
R4-2014367 |
Evaluation on Rel-17 RLM/BFD measurement relaxation |
MediaTek inc. |
R4-2014534 |
Evaluation assumptions for R17 RLM/BFD relaxation |
vivo, MediaTek |
R4-2017270 |
Work plan of Rel-17 Power Saving Enhancements |
MediaTek inc. |
R4-2017306 |
Evaluation assumptions for R17 RLM/BFD relaxation |
vivo, MediaTek |
12.9.2 |
Feasibility and performance impact of relaxing UE measurements for RLM and/or BFD [NR_UE_pow_sav_enh] |
|
R4-2014219 |
Discussion on feasibility and performance impact of RLM/BFD relaxation |
Apple |
R4-2014428 |
Discussion on RLM relaxition for NR power saving |
CATT |
R4-2014535 |
Discussion and initial results for R17 RLM/BFD relaxation |
vivo |
R4-2014654 |
Discussion on RRM measurement relaxation in connected mode for NR power saving enhancement |
Xiaomi |
R4-2014797 |
Discussion on RLM BFD measurement relaxation |
OPPO |
R4-2015199 |
Discussion about evaluation methodology for relaxation of RLM/BFD measurements |
Nokia Solutions & Networks (I) |
R4-2015485 |
Preliminary discussion on RLM/BFD relaxation in power saving enhancements |
Huawei, HiSilicon |
R4-2016150 |
iscussions on UE power saving for RLM and BM |
Ericsson |
R4-2017269 |
WF on NR UE Power Saving Enhancements |
MediaTek |
12.10 |
NR Sidelink enhancement [NRSL_enh] |
|
R4-2016641 |
Email discussion summary for [97e][139] NRSL_enh |
Moderator (LG Electronics) |
R4-2016923 |
WF on the proposed operating bands for NR SL operation in FR1 |
AT&T |
R4-2016980 |
Email discussion summary for [97e][139] NRSL_enh |
Moderator (LG Electronics) |
12.10.1 |
General and work plan [NRSL_enh] |
|
R4-2014326 |
Work plan for SL enhancement for RF perspectives in Rel-17 |
LG Electronics France |
R4-2014973 |
General views on NR sidelink enhancements in R17 |
vivo |
R4-2015256 |
on Rel-17 V2X work |
Xiaomi |
R4-2016281 |
General aspects on RAN4 work for public safety UC support |
Ericsson |
R4-2016484 |
On Rel-17 sidelink enhancement |
Huawei, HiSilicon |
R4-2016924 |
Work plan for SL enhancement for RF perspectives in Rel-17 |
LG Electronics France |
12.10.2 |
Spectrum request for SL operation [NRSL_enh-Core] |
|
R4-2016280 |
spectrum aspect on public saftey UC support |
Ericsson |
R4-2016464 |
NR Sidelink Operating Bands |
AT&T, FirstNet |
13.1 |
Study on enhanced test methods for FR2 in NR [FS_FR2_enhTestMethods] |
|
R4-2014918 |
Updated work plan for FS_FR2_enhTestMethods |
Apple Inc., vivo |
R4-2017429 |
Email discussion summary for [97e][331] FR2_enhTestMethods |
Moderator (Apple) |
R4-2017593 |
WF on remaining open issues with the test methodology for high DL power and low UL power test cases |
Apple |
R4-2017594 |
WF on solutions to minimize the impact of polarization basis mismatch between the TE and DUT on the RF testing |
Samsung |
R4-2017595 |
WF on testability enhancements to support the verification of RF requirements for inter-band (FR2+FR2) CA |
Anritsu |
R4-2017596 |
WF on extreme temperature conditions for all applicable FR2 UE RF test cases |
vivo |
R4-2017597 |
WF on testability enhancements to reduce test time |
vivo |
R4-2017599 |
WF on testability aspects for the introduction of the new band n262 |
Apple |
R4-2017631 |
Email discussion summary for [97e][331] FR2_enhTestMethods |
Moderator (Apple) |
R4-2017663 |
Draft TR38.884 Study on enhanced test methods for FR2 NR UEs v0.1.0 |
Apple, vivo |
R4-2017689 |
WF on solutions to minimize the impact of polarization basis mismatch between the TE and DUT on the RF testing |
Samsung |
13.1.1 |
Test methodology for high DL power and low UL power test cases [FS_FR2_enhTestMethods] |
|
R4-2014267 |
Impact on beam management due to spherical wavefront in DL |
Qualcomm Incorporated |
R4-2014919 |
TP to TR38.884 on High DL and Low UL power test cases |
Apple Inc. |
R4-2015319 |
Test methodology for high DL power and low UL power test cases |
CAICT |
R4-2016213 |
On Test methodology for high DL power and low UL power test cases |
Keysight Technologies UK Ltd |
R4-2016377 |
Impact of phase variation |
MVG Industries, Sony |
R4-2016562 |
Views on test methods for high DL power and low UL power TCs |
ROHDE & SCHWARZ |
R4-2017598 |
TP to TR38.884 on High DL and Low UL power test cases |
Apple Inc., Keysight Technologies, Rohde & Schwarz, MVG Industries |
13.1.2 |
Polarization basis mismatch [FS_FR2_enhTestMethods] |
|
R4-2014266 |
FR2 testability enhancement for polarization mismatch |
Qualcomm Incorporated |
R4-2014725 |
Discussion on FR2 EIRP measurement enhancement |
Samsung |
R4-2014827 |
Analysis on practical TPMI and 2-port CSI-RS for EIRP measurement |
MediaTek Beijing Inc. |
R4-2014920 |
Views on polarization mismatch |
Apple Inc. |
R4-2015871 |
Views on testability enhancement for UE FR2 test |
Sony, Ericsson |
R4-2015872 |
Views on testability enhancement for UE FR2 test |
Sony, Ericsson |
R4-2015895 |
Views on testability enhancement for UE FR2 test |
Sony, Ericsson |
R4-2016212 |
On minimizing the impact of polarization basis mismatch between the TE and DUT |
Keysight Technologies UK Ltd |
R4-2016568 |
Views on polarization basis mismatch |
ROHDE & SCHWARZ |
13.1.3 |
Enhanced test methods for inter-band (FR2+FR2) CA [FS_FR2_enhTestMethods] |
|
R4-2014265 |
On impact of non-co-located test antennae for FR2 inter-band testing |
Qualcomm Incorporated |
R4-2014492 |
Beam correspondence performance measurement improvements of FR2 UEs using carrier aggregation and shared antenna arrays |
Fraunhofer HHI |
R4-2014687 |
Testability of FR2 inter-band DL 2CA EIS by non co-located antenna |
Anritsu corporation |
R4-2014921 |
Impact of AoA offset on inter-band CA PSD difference |
Apple Inc. |
13.1.4 |
Extreme temperature conditions [FS_FR2_enhTestMethods] |
|
R4-2016214 |
On extreme temperature condition testing |
Keysight Technologies UK Ltd |
R4-2016223 |
Views on FR2 extreme condition testing |
vivo |
13.1.6 |
Test time reduction [FS_FR2_enhTestMethods] |
|
R4-2014491 |
Beam sweeping and test time reduction in FR2 |
Fraunhofer HHI, Fraunhofer IIS |
R4-2014726 |
Discussion on FR2 test time reduction |
Samsung |
13.1.7 |
Testability for band n262 [FS_FR2_enhTestMethods] |
|
R4-2014922 |
Band n262 testability |
Apple Inc. |
13.1.7.1 |
Extension of frequency applicability of permitted methods in 38.810 [FS_FR2_enhTestMethods] |
|
R4-2016224 |
Discussion on Testability issue of 47GHz band |
vivo |
13.2.1 |
Numerology, Channel BW [FS_NR_52_to_71GHz] |
|
R4-2016642 |
Email discussion summary for [97e][140] FS_NR_52_to_71GHz_Part_1 |
Moderator (Qualcomm) |
R4-2016925 |
WF on Min and Max Channel Bandwidths in 52 to 71 GHz |
Huawei |
R4-2016926 |
WF on Phase noise mask and PTRS |
Qualcomm |
R4-2016927 |
WF on timing text proposal to TR |
Nokia |
R4-2016928 |
LS on PN models |
RAN4 |
R4-2016981 |
Email discussion summary for [97e][140] FS_NR_52_to_71GHz_Part_1 |
Moderator (Qualcomm) |
R4-2017812 |
Email discussion summary for [97e][140] FS_NR_52_to_71GHz_Part_1 |
Moderator (Qualcomm) |
R4-2017832 |
WF on Min and Max Channel Bandwidths in 52 to 71 GHz |
Huawei |
13.2.1.1 |
General [FS_NR_52_to_71GHz] |
|
R4-2014382 |
Further discussion on numerology and CBW for above 52.6 GHz |
CATT |
R4-2014737 |
Bandwidth and numerology for NR in 52.6GHz |
CMCC |
R4-2014892 |
Further considerations on the numerology and channel bandwidth sizes for the 60GHz frequency range |
Apple Inc. |
R4-2014974 |
Further discussion on channel bandwidths and numerology for B52.6G |
vivo |
R4-2015206 |
Numerology and channel bandwidth discussion for NR beyond 52.6 GHz |
Nokia, Nokia Shanghai Bell |
R4-2015307 |
Channel bandwidth and subcarrier spacing for 52.6 GHz to 71GHz |
NEC |
R4-2015563 |
On numerology and channel bandwidth in 52.6 - 71 GHz |
Intel Corporation |
R4-2015700 |
Discussion on 52.6 GHz to 71 GHz SI |
Huawei, HiSilicon |
R4-2015727 |
On 52.6 to 71 GHz numerology evaluation and channel bandwidths |
Ericsson |
R4-2015886 |
Views on numerologies above 52 GHz |
Sony |
R4-2015890 |
Views on numerologies above 52 GHz |
Sony |
R4-2015891 |
Views on numerologies above 52 GHz |
Sony |
R4-2015892 |
Views on numerologies above 52 GHz |
Sony |
R4-2015893 |
Views on numerologies above 52 GHz |
Sony |
R4-2016110 |
Further discussion on numerology and BW for 52.6GHz-71GHz |
ZTE Corporation |
R4-2016299 |
Subcarrier spacing and minimum channel bandwidth |
Qualcomm Incorporated |
13.2.1.2 |
Timing considerations [FS_NR_52_to_71GHz] |
|
R4-2015991 |
TP to TR 38.808: Timing considerations for operation between 52.6 and 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2016000 |
TP to TR 38.808: Timing considerations for operation between 52.6 and 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2016036 |
TP for NR Rel-17 TR 38.808: Time and synchronization impact |
Ericsson |
13.2.1.3 |
Phase noise and RF impairments related to response to RAN1 [FS_NR_52_to_71GHz] |
|
R4-2014893 |
Futher considerations on the phase noise for the 60GHz frequency range |
Apple Inc. |
R4-2014976 |
TP to TR 38.808: On 52.6 to 71 GHz phase noise characteristics, TP to TR and draft LS to RAN1 |
Ericsson |
R4-2015443 |
Draft LS: Phase noise and RF impairment considerations |
Nokia, Nokia Shanghai Bell |
R4-2015564 |
On 60 GHz Phase noise and RF impairments |
Intel Corporation |
R4-2015728 |
Discussion on PTRS for 52 beyond |
Ericsson |
R4-2016298 |
Phase noise and PTRS |
Qualcomm Incorporated |
R4-2016533 |
on PN model for 60GHz+reply LS RAN1 |
Huawei, HiSilicon |
13.2.2 |
BS aspect [FS_NR_52_to_71GHz] |
|
R4-2014401 |
Discussion on the BS requirements for 52.6-71GHz |
CATT |
R4-2014977 |
TP to TR 38.808: Addition of technical background information for base station in clause 2 and sub-clause 4.2.6 |
Ericsson |
R4-2015200 |
TP to TR 38.808 BS RF for NR beyond 52.6 GHz |
Nokia, Nokia Shanghai Bell |
R4-2015947 |
TP to TR 38.808: BS architecture and BS classes for 52-71 GHz range |
Huawei |
R4-2016643 |
Email discussion summary for [97e][141] FS_NR_52_to_71GHz_Part_2 |
Moderator (Intel) |
R4-2016982 |
Email discussion summary for [97e][141] FS_NR_52_to_71GHz_Part_2 |
Moderator (Intel) |
R4-2016995 |
TP to TR 38.808 BS RF for NR beyond 52.6 GHz |
Nokia, Nokia Shanghai Bell |
R4-2016998 |
WF on FS 52 to 71 GHz |
Intel |
13.2.3 |
UE aspect [FS_NR_52_to_71GHz] |
|
R4-2014975 |
Further discussion on PA model for B52.6G |
vivo |
R4-2015444 |
UE RF for NR beyond 52.6 GHz |
Nokia, Nokia Shanghai Bell |
R4-2015984 |
On power amplifier aspects for UE in the 52.6-71 GHz range |
Ericsson |
R4-2016371 |
A Survey on Memory Based PA Models |
Huawei, HiSilicon |
13.2.4 |
Others [FS_NR_52_to_71GHz] |
|
R4-2014894 |
Regulatory overview and input for the 60GHz frequency range |
Apple Inc. |
R4-2014980 |
TP to TR 38.808: Addition of general RAN4 structure to sub-clause 4.2 |
Ericsson |
R4-2015948 |
TP to TR 38.808: PA trends and typical Noise Figure values |
Huawei |
13.3 |
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths [FS_NR_eff_BW_util] |
|
R4-2016644 |
Email discussion summary for [97e][142] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2016931 |
WF on Irregular Channel Bandwidths |
Ericsson |
R4-2016983 |
Email discussion summary for [97e][142] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2017833 |
WF on Irregular Channel Bandwidths |
Ericsson |
13.3.1 |
General and work plan [FS_NR_eff_BW_util] |
|
R4-2014895 |
Non-standard spectrum allocations for NR bands |
Apple Inc. |
R4-2015721 |
Work Plan for Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidth |
Ericsson |
R4-2015722 |
TR Skeleton on CH BW not aligned with existing BWs |
Ericsson |
R4-2016456 |
Revised SID: Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
T-Mobile USA, Ericsson |
R4-2016929 |
Work Plan for Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidth |
Ericsson |
R4-2016930 |
TR Skeleton on CH BW not aligned with existing BWs |
Ericsson |
13.3.2 |
Input on operator licensed channel bandwidths in FR1 that do not align with existing NR channel bandwidths [FS_NR_eff_BW_util] |
|
R4-2014507 |
UE Support for Irregular Channel Bandwidths - Options and Constraints |
Skyworks Solutions Inc. |
R4-2015723 |
Considerations on Bandwidth Granularity |
Ericsson |
13.3.3 |
Evaluation of use of larger channel bandwidths than operator licensed bandwidth [FS_NR_eff_BW_util] |
|
R4-2015724 |
Utilizing larger CBWs for available spectrum |
Ericsson |
R4-2016111 |
Discussion on irregular channel bandwidth for NR system |
ZTE Corporation |
13.3.4 |
Evaluation of use of overlapping UE channel bandwidths (from both UE and network perspective) [FS_NR_eff_BW_util] |
|
R4-2014487 |
Handling of Channel Bandwidths That Are Not Multiples of 5MHz |
Qualcomm Incorporated |
R4-2015562 |
On efficient utilization of licensed spectrum |
Intel Corporation |
R4-2015713 |
Overlapping UE channel bandwidths |
Huawei, HiSilicon |
13.3.4.1 |
UE perspective [FS_NR_eff_BW_util] |
|
R4-2016201 |
On the use of overlapping channel bandwidths from UE perspective |
Nokia, Nokia Shanghai Bell |
13.3.4.2 |
Network perspective [FS_NR_eff_BW_util] |
|
R4-2016455 |
Use of 5 MHz overlapping channel BWs to cover spectrum blocks between 5 and 10 MHz |
T-Mobile USA |
14.1 |
LTE inter-band Carrier Aggregation for 2 bands DL with 1 band UL [LTE_CA_R17_2BDL_1BUL] |
|
R4-2016645 |
Email discussion summary for [97e][143] LTE_Baskets |
Moderator (Ericsson) |
14.1.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R17_2BDL_1BUL-Core/Perf] |
|
R4-2016232 |
Revised WID: Rel17 LTE inter-band CA for 2 bands DL with 1 band UL |
Qualcomm Incorporated |
R4-2016233 |
Introduction of Rel-17 LTE inter-band CA for 2 bands DL with 1 band UL combinations in TS36.101 |
Qualcomm Incorporated |
R4-2016234 |
TR 36.717-02-01 Rel-17 LTE inter-band CA for 2 bands DL and 1 band UL CA |
Qualcomm Incorporated |
R4-2016992 |
Introduction of Rel-17 LTE inter-band CA for 2 bands DL with 1 band UL combinations in TS36.101 |
Qualcomm Incorporated |
14.1.3 |
UE RF without specific issues [LTE_CA_R17_2BDL_1BUL-Core] |
|
R4-2015392 |
TP for TR 36.717-02-01: CA_2A-8A |
Huawei, HiSilicon |
14.2 |
LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL [LTE_CA_R17_3BDL_1BUL] |
|
R4-2014067 |
TP for TR 36.717-03-01: CA_1-8-41 |
VODAFONE Group Plc |
R4-2014068 |
TP for TR 36.717-03-01: CA_1-40-41 |
VODAFONE Group Plc |
R4-2014069 |
TP for TR 36.717-03-01: CA_8-40-41 |
VODAFONE Group Plc |
R4-2016768 |
TP for TR 36.717-03-01: CA_1-40-41 |
VODAFONE Group Plc |
R4-2016769 |
TP for TR 36.717-03-01: CA_8-40-41 |
VODAFONE Group Plc |
14.2.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R17_3BDL_1BUL-Core/Perf] |
|
R4-2016541 |
Introduction of completed R17 3DL band combinations to TS 36.101 |
Huawei, HiSilicon |
R4-2016542 |
Revised WID for LTE inter-band CA for 3 bands DL with 1 bands UL |
Huawei, HiSilicon |
14.3 |
LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL |
|
R4-2014065 |
TP for TR 36.717-04-01: CA_1-3-8-41 |
VODAFONE Group Plc |
R4-2015201 |
Extension of LTE iterbCA 4/5 WI to include 6 bands |
VODAFONE Group Plc |
R4-2016767 |
TP for TR 36.717-04-01: CA_1-3-8-41 |
VODAFONE Group Plc |
14.3.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R17_xBDL_1BUL-Core] |
|
R4-2015070 |
Introduction of LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL to TS36.101 |
Nokia, Nokia Shanghai Bell |
R4-2016181 |
Revised WID: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2016182 |
Updated scope of TR: LTE inter-band CA for 4/5 bands DL with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2016183 |
TR 36.717-04-01 v0.2.0 |
Nokia, Nokia Shanghai Bell |
14.3.2 |
UE RF with 4 LTE bands CA [LTE_CA_R17_xBDL_1BUL-Core] |
|
R4-2015393 |
Draft CR to 36.101 to add configuration CA_1A-3A-8A-40C |
Huawei, HiSilicon |
R4-2015394 |
Draft CR to 36.101 to add CA_1A-3C-7A-8A with UL CA_3C |
Huawei, HiSilicon |
R4-2015395 |
TP for TR 36.717-04-01: CA_1A-7A-8A-38A |
Huawei, HiSilicon |
R4-2015396 |
TP for TR 36.717-04-01: CA_1A-8A-20A-38A |
Huawei, HiSilicon |
R4-2015397 |
TP for TR 36.717-04-01: CA_3A-8A-20A-38A |
Huawei, HiSilicon |
R4-2015398 |
TP for TR 36.717-04-01: CA_1A-3C-8A-38A with UL CA_3C |
Huawei, HiSilicon |
R4-2015399 |
TP for TR 36.717-04-01: CA_1A-3C-8A-20A with UL CA_3C |
Huawei, HiSilicon |
R4-2015400 |
Updated TP for TR 36.717-04-01: CA_1A-3C-20A-38A with UL CA_3C |
Huawei, HiSilicon |
R4-2015402 |
Updated TP for TR 36.717-04-01: CA_2A-5A-7A-66A-66A |
Huawei, HiSilicon |
R4-2016770 |
TP for TR 36.717-04-01: CA_1A-7A-8A-38A |
Huawei, HiSilicon |
R4-2016771 |
TP for TR 36.717-04-01: CA_1A-8A-20A-38A |
Huawei, HiSilicon |
R4-2016772 |
TP for TR 36.717-04-01: CA_3A-8A-20A-38A |
Huawei, HiSilicon |
R4-2016773 |
TP for TR 36.717-04-01: CA_1A-3C-8A-38A with UL CA_3C |
Huawei, HiSilicon |
R4-2016774 |
TP for TR 36.717-04-01: CA_1A-3C-8A-20A with UL CA_3C |
Huawei, HiSilicon |
R4-2016775 |
Updated TP for TR 36.717-04-01: CA_1A-3C-20A-38A with UL CA_3C |
Huawei, HiSilicon |
14.3.3 |
UE RF with 5 LTE bands CA [LTE_CA_R17_xBDL_1BUL-Core] |
|
R4-2015401 |
TP for TR 36.717-04-01: CA_1A-3A-7A-8A-40A / CA_1A-3A-7A-8A-40C |
Huawei, HiSilicon |
R4-2016776 |
TP for TR 36.717-04-01: CA_1A-3A-7A-8A-40A / CA_1A-3A-7A-8A-40C |
Huawei, HiSilicon |
14.4.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R17_2BDL_2BUL-Core] |
|
R4-2016488 |
Introduction of completed R17 2DL2UL band combinations to TS 36.101 |
Huawei, HiSilicon |
R4-2016489 |
Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL |
Huawei, HiSilicon |
14.5.1 |
Rapporteur Input (WID/TR/CR) [LTE_CA_R17_xBDL_2BUL-Core] |
|
R4-2014300 |
TR 36.717-03-02 v0.2.0 TR Update for LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics Polska |
R4-2014301 |
Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics Polska |
R4-2014302 |
Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 |
LG Electronics Polska |
14.6.2 |
RRM Perf (36.133) [LTE_CA_R17_xxxx-Perf] |
|
R4-2016646 |
Email discussion summary for [97e][144] LTE_bands_R17_M1_M2_NB1_NB2 |
Moderator (Ercisson) |
R4-2016932 |
WF on A-MPR simulation assumption for B24 CAT-M1/M2 device |
Ligado Networks |
R4-2016984 |
Email discussion summary for [97e][144] LTE_bands_R17_M1_M2_NB1_NB2 |
Moderator (Ercisson) |
14.7.1 |
Rapporteur Input (WID/TR/CR) [LTE_bands_R17_M1_M2_NB1_NB2-Core] |
|
R4-2016266 |
CR of adding LTE B24 for UE category NB1 in R17 |
Ericsson, Ligado Networks |
R4-2016267 |
CR of adding LTE B24 for UE category NB1 in R17 |
Ericsson, Ligado Networks |
R4-2016268 |
CR of adding LTE B24 for UE category NB1 in R17 |
Ericsson, Ligado Networks |
R4-2016269 |
CR of adding LTE B24 for UE category NB1 in R17 |
Ericsson, Ligado Networks |
R4-2016270 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016271 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016272 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016274 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016276 |
CR of adding LTE B24 for UE category NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016277 |
CR of adding LTE B24 for UE category NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016278 |
CR of adding LTE B24 for UE category NB2 in R17 |
Ericsson, Ligado Networks |
14.7.2 |
RF [LTE_bands_R17_M1_M2_NB1_NB2-Core] |
|
R4-2015794 |
Band 24 Cat M1/M2 A-MPR assumptions |
Ligado Networks |
R4-2016279 |
Further consideration of A-MPR simulation assumption for B24 |
Ericsson |
14.7.3 |
Others [LTE_bands_R17_M1_M2_NB1_NB2-Perf] |
|
R4-2016273 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
R4-2016275 |
CR of adding LTE B24 for UE category NB1/NB2 in R17 |
Ericsson, Ligado Networks |
14.8.2 |
UE RF [LTE_B24_mod-Core] |
|
R4-2014161 |
Band 24 UE additional emissions requirements, A-MPR scenarios and assumptions, and UE REFSENS |
Ligado Networks |
14.8.3 |
BS RF [LTE_B24_mod-Core] |
|
R4-2016197 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016198 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016199 |
Draft CR to 37.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016200 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016888 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016889 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016890 |
Draft CR to 37.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
R4-2016891 |
Draft CR to 36.104: Correction to Band 24 requirements (Rel-10) |
Nokia, Nokia Shanghai Bell |
14.8.4 |
RRM and others [LTE_B24_mod-Core/Perf] |
|
R4-2014191 |
Draft CR for 37.105: Corrections related to Band 24 regulatory updates (Rel-15) |
Ligado Networks |
R4-2014192 |
Draft CR for TS 37.105 Corrections related to Band 24 regulatory updates (Rel-16) |
Ligado Networks |
R4-2014193 |
Draft CR for TS 37.105 Corrections related to Band 24 regulatory updates (Rel-17) |
Ligado Networks |
R4-2014194 |
Draft CR for 37.145-1: Corrections related to Band 24 regulatory updates (Rel-13) |
Ligado Networks |
R4-2014195 |
Draft CR for TS 37.145-1 Corrections related to Band 24 regulatory updates (Rel-14) |
Ligado Networks |
R4-2014196 |
Draft CR for TS 37.145-1 Corrections related to Band 24 regulatory updates (Rel-15) |
Ligado Networks |
R4-2014197 |
Draft CR for TS 37.145-1 Corrections related to Band 24 regulatory updates (Rel-16) |
Ligado Networks |
R4-2014198 |
Draft CR for TS 37.145-1 Corrections related to Band 24 regulatory updates (Rel-17) |
Ligado Networks |
R4-2014199 |
Draft CR for 37.145-2: Corrections related to Band 24 regulatory updates (Rel-15) |
Ligado Networks |
R4-2014200 |
Draft CR for TS 37.145-2 Corrections related to Band 24 regulatory updates (Rel-16) |
Ligado Networks |
R4-2014201 |
Draft CR for TS 37.145-2 Corrections related to Band 24 regulatory updates (Rel-17) |
Ligado Networks |
R4-2016885 |
Draft CR for 37.105: Corrections related to Band 24 regulatory updates (Rel-15) |
Ligado Networks |
R4-2016886 |
Draft CR for 37.145-1: Corrections related to Band 24 regulatory updates (Rel-13) |
Ligado Networks |
R4-2016887 |
Draft CR for 37.145-2: Corrections related to Band 24 regulatory updates (Rel-15) |
Ligado Networks |
15.1 |
High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands 5 and 12 and NR band n71 [FS_LTE_NR_HPUE_FWVM] |
|
R4-2016647 |
Email discussion summary for [97e][145] FS_LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2016933 |
Updated Work Plan for Study on High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 |
Nokia |
R4-2016934 |
TP to TR 37.880: Coexistence Simulation Results and Observations for High-power UE operation Vs NB-IoT standalone operation |
Nokia, Nokia Shanghai Bell |
R4-2016985 |
Email discussion summary for [97e][145] FS_LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
15.1.1 |
General |
|
R4-2014479 |
TR 37.880 V0.1.0: High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 |
Nokia, Nokia Shanghai Bell |
15.1.2 |
Coexistence study |
|
R4-2014480 |
Coexistence Simulation Results for High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 |
Nokia, Nokia Shanghai Bell |
15.1.3 |
UE RF |
|
R4-2014481 |
TP to TR 37.880: High-power UE transmitter/receiver architecture for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, and Band n71 |
Nokia, Nokia Shanghai Bell |
17.1 |
Simplification of band combinations in RAN4 specifications |
|
R4-2014482 |
On a request sheet/WID template for band combinations |
Nokia, Nokia Shanghai Bell |
R4-2014598 |
More on an alternative to creating new BCSs |
Nokia, Nokia Shanghai Bell |
R4-2014959 |
Further considerations on simplification of band combination |
ZTE Corporation |
R4-2014960 |
CR to TS 38.101-1 on simplification for inter-band CA configuration |
ZTE Corporation |
R4-2014961 |
CR to TS 38.101-2 on simplification for inter-band CA configuration |
ZTE Corporation |
R4-2014962 |
CR to TS 38.101-3 on simplification for inter-band CA configuration between FR1 and FR2 |
ZTE Corporation |
R4-2015320 |
Further consideration on simplification of band configuration |
NTT DOCOMO INC. |
R4-2015546 |
To update the coversheet of Excel table based on the Rel-17 band combination basket WI |
Huawei, HiSilicon |
R4-2016007 |
LTE Rel |
Skyworks Solutions Inc. |
R4-2016297 |
CA/DC Band configurations notations and usage in 3GPP |
Apple |
R4-2016453 |
An alternative to creating new BCSs |
T-Mobile USA, Deutsche Telekom, AT&T, TELUS, Bell Mobility, Rogers Communications, Telstra, Telecom Italia, KDDI, Vodafone, BT plc, Ericsson |
R4-2016454 |
Draft CR for 38.101-1: Introduction of BCS4 |
T-Mobile USA |
R4-2016457 |
NR-CA and NR-DC 3 band requests and fallbacks |
T-Mobile USA, TELUS, Bell Mobility, AT&T |
R4-2016648 |
Email discussion summary for [97e][146] BC_simplification |
Moderator (NTT DOCOMO) |
R4-2016935 |
WF on rules on request sheet and notations of CA/DC configurations |
Apple |
R4-2016936 |
WF on updating cover sheet of request sheet |
NTT DOCOMO.,INC. |
R4-2016937 |
CR to TS 38.101-1 on simplification for inter-band CA configuration |
ZTE Corporation |
R4-2016938 |
CR to TS 38.101-2 on simplification for inter-band CA configuration |
ZTE Corporation |
R4-2016939 |
CR to TS 38.101-3 on simplification for inter-band CA configuration between FR1 and FR2 |
ZTE Corporation |
R4-2016940 |
WF on MSD test point specification methodology for LTE CA |
Skyworks |
R4-2016941 |
WF on alternative to creating new BCSs |
T-Mobile USA |
R4-2016986 |
Email discussion summary for [97e][146] BC_simplification |
Moderator (NTT DOCOMO) |
R4-2017836 |
WF on alternative to creating new BCSs |
T-Mobile USA |
R4-2017843 |
WF on alternative to creating new BCSs |
T-Mobile USA |
17.2.1 |
Spectrum related |
|
R4-2015285 |
New basket WID on bands with UL-MIMO PC3 |
Huawei, HiSilicon |
R4-2015909 |
New WI: Specification of band n67 |
Ericsson |
R4-2016543 |
New basket WID NR_PC2_CA_R17_intra |
Huawei, HiSilicon |
R4-2017819 |
New WID: Introduction of BCS4 |
T-Mobile USA |
R4-2017820 |
Motivation for BCS4 |
T-Mobile USA |
17.2.2 |
Non-spectrum related |
|
R4-2014352 |
Motivation for new WI on air-to-ground network for NR |
CMCC |
R4-2014353 |
New WID on air-to-ground network for NR |
CMCC |
R4-2014594 |
Proposal to extend R17 FeRRM WI scope |
Apple |
R4-2015115 |
Discssion on EMC Test Simplification for Rel-17 EMC enhancement |
Ericsson |
R4-2015116 |
New WID proposal on RAN4 Rel-17 EMC enhancement |
Ericsson, ZTE |
R4-2015254 |
[UE EMC] Further discussion on UE EMC enhancement |
Xiaomi |
R4-2015670 |
New objectives for Rel-17 demodulation performance work item |
Huawei, HiSilicon |
R4-2016002 |
CRS-IC requirements for LTE-NR coexistence scenario |
Intel Corporation |
R4-2016180 |
Email summary of UE and BS EMC discussion |
Ericsson |
R4-2016230 |
Motivation for WI: NR FR1 UE SA and EN-DC TRP and TRS |
vivo |
R4-2016231 |
New WID: NR FR1 UE SA and EN-DC TRP and TRS |
vivo, OPPO, CMCC, CAICT, Rohde & Schwarz |
18 |
Any other business |
|
R4-2014327 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2014328 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2014329 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2016942 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2016943 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
R4-2016944 |
LTE/NR spectrum sharing in Band 40/n40 |
Reliance Jio |
19 |
Close of the E-meeting |
|
R4-2017392 |
(reserved) |
RRM Session |